Triple
T34018065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam-Utrecht corridor |
E872301
|
entity |
| Predicate | mainRailAxis |
P109925
|
FINISHED |
| Object | Amsterdam–Utrecht railway |
—
|
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: Amsterdam–Utrecht railway | Statement: [Amsterdam-Utrecht corridor, mainRailAxis, Amsterdam–Utrecht railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRailAxis Context triple: [Amsterdam-Utrecht corridor, mainRailAxis, Amsterdam–Utrecht railway]
-
A.
primaryRailLinkFor
chosen
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
B.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
C.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
D.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
E.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:51 a.m.