Triple
T31736528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Drummond (locomotive engineer) |
E810011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish engineer |
C13799
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Scottish engineer Context triple: [Peter Drummond (locomotive engineer), instanceOf, Scottish engineer]
-
A.
British engineer
chosen
A British engineer is a professional from the United Kingdom who applies scientific and mathematical principles to design, develop, and maintain technological systems, structures, and processes across various engineering disciplines.
-
B.
German-born British inventor
A German-born British inventor is an individual originally from Germany who later became a British national and is recognized for creating or significantly improving devices, processes, or technologies.
-
C.
Canadian engineer
A Canadian engineer is a professional trained in engineering disciplines who applies scientific and technical knowledge to design, develop, and maintain systems, structures, or technologies within the context of Canadian standards, regulations, and societal needs.
-
D.
French-American engineer
A French-American engineer is a professional with dual French and American cultural or national backgrounds who applies engineering principles to design, analyze, and improve systems, structures, or technologies.
-
E.
Scottish physician
A Scottish physician is a medical doctor from Scotland who diagnoses, treats, and helps prevent illness and injury in patients while often contributing to public health and medical research.
- F. None of above.
Provenance (1 batch)
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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:23 p.m.