Triple
T29572223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman engineering |
E753343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering tradition |
C55911
|
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: engineering tradition Context triple: [Roman engineering, instanceOf, engineering tradition]
-
A.
military engineering tradition
A military engineering tradition is the historically developed body of practices, knowledge, values, and institutional norms that guide how a society designs, constructs, and employs engineering solutions for military purposes across time.
-
B.
engineering dynasty
An engineering dynasty is a lineage or family whose successive generations significantly influence and advance engineering practice, innovation, and leadership over an extended period.
-
C.
engineering profession
The engineering profession is a field in which individuals apply scientific, mathematical, and technical knowledge to design, develop, and optimize systems, structures, and technologies that solve practical problems and improve society.
-
D.
engineering institute
An engineering institute is an educational and research organization dedicated to teaching, advancing, and applying engineering principles and technologies across various specialized fields.
-
E.
engineering treatise
An engineering treatise is a comprehensive, systematically organized written work that rigorously analyzes, explains, and documents engineering principles, methods, designs, or systems.
- F. None of above. chosen
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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 5:59 p.m.