Triple
T34694303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMS Armstrong Whitworth |
E890982
|
entity |
| Predicate | locomotiveClassBuiltFor |
P179766
|
FINISHED |
| Object | Black Five |
—
|
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: Black Five | Statement: [LMS Armstrong Whitworth, locomotiveClassBuiltFor, Black Five]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotiveClassBuiltFor Context triple: [LMS Armstrong Whitworth, locomotiveClassBuiltFor, Black Five]
-
A.
typicalLocomotiveClass
Indicates that one locomotive class is the standard or most commonly used class for a given context, operator, or service.
-
B.
railwayBuiltFor
Indicates that a railway was constructed to serve, support, or provide access to a particular entity or purpose.
-
C.
laterLocomotiveType
Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
-
D.
primaryLocomotiveType
Indicates the main method or mechanism by which an entity typically moves or travels.
-
E.
locomotiveName
Indicates that a locomotive has a specific name assigned to it.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 2:05 a.m.