Triple
T37098462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crewe–Birmingham railway line |
E918629
|
entity |
| Predicate | linksCityCentre |
P84283
|
FINISHED |
| Object | Birmingham city centre |
—
|
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: Birmingham city centre | Statement: [Crewe–Birmingham railway line, linksCityCentre, Birmingham city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksCityCentre Context triple: [Crewe–Birmingham railway line, linksCityCentre, Birmingham city centre]
-
A.
cityCentreAccess
chosen
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
B.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
C.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
D.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
E.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.