Triple
T32371464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E313 motorway |
E827147
|
entity |
| Predicate | formsTransportAxisBetween |
P70574
|
FINISHED |
| Object | Port of Antwerp |
—
|
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 of Antwerp | Statement: [E313 motorway, formsTransportAxisBetween, Port of Antwerp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsTransportAxisBetween Context triple: [E313 motorway, formsTransportAxisBetween, Port of Antwerp]
-
A.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
B.
formsAxisOf
Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
-
C.
formsTransportCorridorBetween
chosen
Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
-
D.
transportedBetween
Indicates that an entity is moved or conveyed from one specified location or state to another.
-
E.
formsTransitSpineFor
Indicates that one element serves as the primary transit corridor or backbone that structurally supports and organizes movement for another.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:50 a.m.