Triple
T30259606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great North Eastern Railway |
E769449
|
entity |
| Predicate | railwayCompanyCode |
P179235
|
FINISHED |
| Object | GR |
—
|
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: GR | Statement: [Great North Eastern Railway, railwayCompanyCode, GR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayCompanyCode Context triple: [Great North Eastern Railway, railwayCompanyCode, GR]
-
A.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
B.
railwayCompanyType
Indicates the specific category or classification of a railway company in terms of its role, ownership, or operational type.
-
C.
railwayCompanyOnRoute
Indicates that a particular railway company operates or provides service on a specified route.
-
D.
railwayCompanyGroup
Indicates that one entity is a group or consortium that includes or controls the other entity as a railway company.
-
E.
laterRailwayCompany
Indicates that one railway company is the successor or later incarnation of another railway company.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 29, 2026, 7:41 p.m.