Triple
T38675891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tampa |
E943737
|
entity |
| Predicate | portCityInvolved |
P191514
|
FINISHED |
| Object | Tampa |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Tampa | Statement: [Battle of Tampa, portCityInvolved, Tampa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portCityInvolved Context triple: [Battle of Tampa, portCityInvolved, Tampa]
-
A.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
B.
isPortCityOn
Indicates that a city functions as a port located on the specified body of water.
-
C.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
D.
isAmongLargestPortsIn
Indicates that a port ranks among the largest ports within a specified geographic or administrative area.
-
E.
majorPortCity
Indicates that a city functions as a primary maritime port, serving as a major hub for sea transport, trade, or shipping activities.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.