Triple
T25318934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTPAP |
E634823
|
entity |
| Predicate | isPrincipalSeaportFor |
P53991
|
FINISHED |
| Object | Port-au-Prince |
—
|
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: Port-au-Prince | Statement: [HTPAP, isPrincipalSeaportFor, Port-au-Prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrincipalSeaportFor Context triple: [HTPAP, isPrincipalSeaportFor, Port-au-Prince]
-
A.
hasSeaportStatus
Indicates that an entity possesses the status or designation of being a seaport or having seaport facilities.
-
B.
isMainDeepWaterPortFor
chosen
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
-
C.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
D.
isCommercialPort
Indicates that a location functions as a port used for commercial or trade-related maritime activities.
-
E.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 1:28 p.m.