Triple
T38136441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Board of Engineers for Fortifications |
E952364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military engineering board |
C39173
|
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: military engineering board Context triple: [U.S. Board of Engineers for Fortifications, instanceOf, military engineering board]
-
A.
military engineering system
A military engineering system is an integrated framework of technologies, processes, and organizational structures designed to plan, construct, maintain, and protect military infrastructure and capabilities in support of defense operations.
-
B.
army engineer
An army engineer is a military specialist who designs, constructs, and maintains infrastructure and systems to support combat operations and logistical needs in diverse and often hostile environments.
-
C.
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.
-
D.
corps of engineers
chosen
A corps of engineers is an organized body of military or civilian engineers responsible for planning, designing, constructing, and maintaining infrastructure and technical projects, often in support of national defense or public works.
-
E.
civil engineer squadron
A civil engineer squadron is a military unit responsible for planning, constructing, maintaining, and repairing infrastructure and facilities to support operational readiness and base sustainability.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.