Triple
T23212990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodmin and Wenford Railway |
E580651
|
entity |
| Predicate | grantedLightRailwayOrder |
P151383
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Bodmin and Wenford Railway, grantedLightRailwayOrder, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedLightRailwayOrder Context triple: [Bodmin and Wenford Railway, grantedLightRailwayOrder, 1990]
-
A.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
B.
lightRailNetwork
Indicates a relationship where an area, city, or region is served by or contains a light rail transit network.
-
C.
hasLightRailStationPlanned
Indicates that a light rail station is planned or scheduled to be built at or associated with the given entity.
-
D.
lightRailSystemName
Indicates the name assigned to a particular light rail transit system.
-
E.
lightRailExpansion
Indicates the process or plan of extending an existing light rail transit system to cover additional areas or routes.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19162c77c8190ba29c59ea9695316 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:07 p.m.