Triple
T4284038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Rotterdam |
E97221
|
entity |
| Predicate | hasPipelineConnection |
P55206
|
FINISHED |
| Object | European petrochemical network |
—
|
LITERAL FINISHED |
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: European petrochemical network | Statement: [Port of Rotterdam, hasPipelineConnection, European petrochemical network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPipelineConnection Context triple: [Port of Rotterdam, hasPipelineConnection, European petrochemical network]
-
A.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
B.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
C.
hasTrailConnection
Indicates that one location is connected to another by a traversable trail or path.
-
D.
hasInlet
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503c062c81908f9a9eeab5381ec9 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.