Triple
T35006335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blisworth Cutting |
E1009818
|
entity |
| Predicate | railwayOpenedBy |
P185355
|
FINISHED |
| Object | London and Birmingham Railway Company |
—
|
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: London and Birmingham Railway Company | Statement: [Blisworth Cutting, railwayOpenedBy, London and Birmingham Railway Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayOpenedBy Context triple: [Blisworth Cutting, railwayOpenedBy, London and Birmingham Railway Company]
-
A.
railwayOpenedWith
Indicates that a railway line or section was inaugurated and began operation together with a specified associated element (such as a station, segment, or service).
-
B.
laterRailwayCompany
Indicates that one railway company is the successor or later incarnation of another railway company.
-
C.
railwayWorksOpened
Indicates that a railway facility, such as a station, line, or related infrastructure, was officially opened or began operation on a specified date.
-
D.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
E.
railwayLineOpened
Indicates that a railway line began official operation or service on a specified date.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 3, 2026, 4:01 p.m.