Triple
T24050365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Caney, near Santiago de Cuba, Cuba |
E595640
|
entity |
| Predicate | hasNearbyMajorPortCity |
P151712
|
FINISHED |
| Object | Santiago de Cuba |
—
|
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: Santiago de Cuba | Statement: [El Caney, near Santiago de Cuba, Cuba, hasNearbyMajorPortCity, Santiago de Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMajorPortCity Context triple: [El Caney, near Santiago de Cuba, Cuba, hasNearbyMajorPortCity, Santiago de Cuba]
-
A.
hasNearbyMajorCityCountry
Indicates that an entity has a nearby major city located in the specified country.
-
B.
majorCityNearMouth
Indicates that a major city is located close to the mouth (outflow point) of a river.
-
C.
nearbyCityOrPort
chosen
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
D.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
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.
Provenance (3 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cfb914819091a3378518f9f28d |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:20 p.m.