Triple
T3053405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BHM |
E60422
|
entity |
| Predicate | associatedWithStationCategory |
P8936
|
FINISHED |
| Object | major city centre 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: major city centre station | Statement: [BHM, associatedWithStationCategory, major city centre station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithStationCategory Context triple: [BHM, associatedWithStationCategory, major city centre station]
-
A.
associatedStationCategory
chosen
Indicates that one entity is linked to, or classified under, a particular category of station.
-
B.
associatedWithStationName
Indicates a relationship where something is linked or connected to a particular station identified by its name.
-
C.
associatedStationCountry
Indicates that there is a relationship linking a station to the country with which it is associated.
-
D.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
E.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf51b5081908ce355a76cfa9e3c |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.