Triple
T32912237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grange Hill tube station |
E841909
|
entity |
| Predicate | railwayEnquirySystemCode |
P181275
|
FINISHED |
| Object | 9100GRNGH |
—
|
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: 9100GRNGH | Statement: [Grange Hill tube station, railwayEnquirySystemCode, 9100GRNGH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayEnquirySystemCode Context triple: [Grange Hill tube station, railwayEnquirySystemCode, 9100GRNGH]
-
A.
railwayEnquirySystem
Indicates a system or service that provides information and answers queries related to railway schedules, services, and operations.
-
B.
railwayStationOnLine
Indicates that a particular railway station is located on and served by a specified railway line.
-
C.
railwayCodeType
Indicates the specific classification or type category assigned to a railway code within a railway coding system.
-
D.
railwayName
Indicates the name assigned to a specific railway or railway line in the relationship.
-
E.
railcodeSystem
Indicates a relationship where a rail-specific code is assigned to, used by, or governs a particular system within a railway context.
- F. None of above. chosen
Provenance (4 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:19 a.m.