Triple
T37187926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westwijk |
E921368
|
entity |
| Predicate | servedByFormerMetroLine |
P126423
|
FINISHED |
| Object | Amsterdam Metro line 51 |
—
|
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 Metro line 51 | Statement: [Westwijk, servedByFormerMetroLine, Amsterdam Metro line 51]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByFormerMetroLine Context triple: [Westwijk, servedByFormerMetroLine, Amsterdam Metro line 51]
-
A.
servedByTramwayLine
Indicates that a location or area is provided public transport service by a specific tramway line.
-
B.
connectsToMetroLineAt
Indicates that one location or transportation facility is directly linked or provides access to a specific metro line at a particular point.
-
C.
railroadLineServed
Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
-
D.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
E.
formerLineServed
chosen
Indicates that a particular transit line previously provided service to a route, station, or area but no longer does so.
- 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_6a0061454944819088a0babfe60f69fc |
completed | May 10, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_6a0060b9ee108190b91e8d99a16f2b30 |
completed | May 10, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:15 p.m.