Triple
T30255103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE U36B |
E769316
|
entity |
| Predicate | locomotiveSeries |
P169027
|
FINISHED |
| Object | U36 series |
—
|
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: U36 series | Statement: [GE U36B, locomotiveSeries, U36 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotiveSeries Context triple: [GE U36B, locomotiveSeries, U36 series]
-
A.
usedInLocomotiveSeries
Indicates that something is employed or implemented within a particular locomotive series.
-
B.
laterLocomotiveType
Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
-
C.
notableLocomotiveModels
Indicates a relationship where specific locomotive models are recognized as notable or significant examples associated with an entity (such as a manufacturer, railway, or time period).
-
D.
typicalLocomotiveClass
Indicates that one locomotive class is the standard or most commonly used class for a given context, operator, or service.
-
E.
locomotiveWorks
Indicates a relationship where an entity is a facility or company that builds, repairs, or maintains locomotives.
- 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_69f6807ef98081908c934c38b7448740 |
completed | May 2, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:41 p.m.