Triple
T12888980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isambard Kingdom Brunel |
E308306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Victorian 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: Victorian engineer Context triple: [Isambard Kingdom Brunel, instanceOf, Victorian 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.
16th-century engineer
A 16th-century engineer is a technically skilled practitioner who designs, constructs, and improves machines, fortifications, and infrastructure using emerging scientific principles and practical craftsmanship within the social and technological context of the Renaissance.
-
C.
locomotive designer
A locomotive designer is a specialist who conceptualizes, engineers, and refines the structure, mechanics, and aesthetics of locomotives to meet performance, safety, and operational requirements.
-
D.
locomotive designer
A locomotive designer is a professional who conceptualizes, engineers, and refines the structure, systems, and aesthetics of locomotives to meet performance, safety, and regulatory requirements.
-
E.
member of the Brunel family
A member of the Brunel family is an individual belonging to the historically significant Brunel lineage, noted for its influential engineers and their contributions to industrial and civil engineering.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:39 p.m.