Triple
T31593832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland Railway – Butterley |
E806169
|
entity |
| Predicate | hasHeadquartersStation |
P52556
|
FINISHED |
| Object | Butterley railway station |
—
|
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: Butterley railway station | Statement: [Midland Railway – Butterley, hasHeadquartersStation, Butterley railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadquartersStation Context triple: [Midland Railway – Butterley, hasHeadquartersStation, Butterley railway station]
-
A.
headquartersStation
chosen
Indicates that a particular station serves as the main headquarters location for an organization or entity.
-
B.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
C.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
D.
hasStationInCity
Indicates that a station or facility is located within a particular city.
-
E.
hasFocalStations
Indicates that an entity is associated with one or more primary or central stations that serve as its main points of focus or operation.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 30, 2026, 10:29 p.m.