Triple
T34159169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia–Europe |
E876225
|
entity |
| Predicate | hasKeyEuropeanPort |
P190381
|
FINISHED |
| Object | Rotterdam |
—
|
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: Rotterdam | Statement: [Asia–Europe, hasKeyEuropeanPort, Rotterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyEuropeanPort Context triple: [Asia–Europe, hasKeyEuropeanPort, Rotterdam]
-
A.
isBalticPortRegion
Indicates that a region functions as a port area located on or directly connected to the Baltic Sea.
-
B.
lastEuropeanPortOfCall
Indicates the final European port at which a vessel or traveler stopped before departing for a non-European destination.
-
C.
hasEuropeanRoute
Indicates that a road or segment is designated as part of a specific European route within the trans-European road network.
-
D.
isBalticPortCity
Indicates that a city functions as a port located on the Baltic Sea.
-
E.
hasInternationalPort
Indicates that an entity possesses a port facility that supports international transportation or trade connections.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:54 a.m.