Triple
T37114859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nhava Sheva International Container Terminal |
E919089
|
entity |
| Predicate | portUNLocode |
P1492
|
FINISHED |
| Object | INNSA |
—
|
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: INNSA | Statement: [Nhava Sheva International Container Terminal, portUNLocode, INNSA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portUNLocode Context triple: [Nhava Sheva International Container Terminal, portUNLocode, INNSA]
-
A.
portCodeLOCODE
Indicates that a port is identified by a specific LOCODE (Location Code) value.
-
B.
hasUNLocode
chosen
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
C.
portOfLoading
Indicates the location where goods are initially loaded onto a vessel or transport vehicle for shipment.
-
D.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
E.
UNLocodeStatus
Indicates the current official status or validity of a UN/LOCODE entry within the UN location code system.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.