Triple
T23764169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 08 |
E587330
|
entity |
| Predicate | standardShunterFor |
P153870
|
FINISHED |
| Object | British Rail |
—
|
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: British Rail | Statement: [British Rail Class 08, standardShunterFor, British Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardShunterFor Context triple: [British Rail Class 08, standardShunterFor, British Rail]
-
A.
standardStartRule
Indicates that something begins or is initiated according to a defined standard or default rule.
-
B.
standardParallelType
Indicates the type or method by which the standard parallel(s) are defined or specified in a coordinate reference or map projection system.
-
C.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
D.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
E.
uniformBranch
Indicates that multiple entities share the same branch, division, or organizational unit within a larger structure.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb4e9248190b64b063637b66702 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:14 p.m.