Triple
T32523831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbesthal |
E831251
|
entity |
| Predicate | formerStationType |
P186105
|
FINISHED |
| Object | international railway station |
—
|
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: international railway station | Statement: [Herbesthal, formerStationType, international railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerStationType Context triple: [Herbesthal, formerStationType, international railway station]
-
A.
formerStationCode
Indicates that an entity previously had a specific station code that is no longer in current use.
-
B.
formerStationNameFor
Indicates that one station name was previously used as the official name for another station.
-
C.
formerStationOnLine
Indicates that a station previously belonged to or operated on a particular transit line but is no longer in service on that line.
-
D.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
E.
hadStationType
chosen
Indicates that an entity (such as a station) possessed or was classified by a particular type or category of station.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 1, 2026, 1:01 a.m.