Triple
T37187927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westwijk |
E921368
|
entity |
| Predicate | roleOnMetroLine51 |
P17559
|
FINISHED |
| Object | southern terminus |
—
|
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: southern terminus | Statement: [Westwijk, roleOnMetroLine51, southern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnMetroLine51 Context triple: [Westwijk, roleOnMetroLine51, southern terminus]
-
A.
isFirstMetroLineInCity
Indicates that a metro line is the earliest or original metro line established in a given city.
-
B.
precededByStationOnLine5
Indicates that one station directly comes before another station in the ordered sequence of stations on line 5.
-
C.
hasMetroLine
chosen
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
D.
isOnAutomatedMetroLine
Indicates that something (typically a metro station, segment, or service) belongs to or operates on a metro line that runs with automated (driverless or semi-driverless) train control.
-
E.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:15 p.m.