Triple
T5255810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organisation Todt |
E118693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil and military engineering organization |
C298
|
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: civil and military engineering organization Context triple: [Organisation Todt, instanceOf, civil and military engineering organization]
-
A.
U.S. Army Corps of Engineers district
A U.S. Army Corps of Engineers district is a regional organizational unit responsible for planning, designing, constructing, and managing civil works and military projects within a defined geographic area.
-
B.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
C.
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.
-
D.
group of civil engineers
A group of civil engineers is a collaborative team of professionals who plan, design, and oversee the construction and maintenance of infrastructure projects such as roads, bridges, buildings, and water systems.
-
E.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.