Triple
T6399426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Research and Development Organisation |
E144024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence research agency |
C18934
|
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: defence research agency Context triple: [Defence Research and Development Organisation, instanceOf, defence research agency]
-
A.
defense research agency
chosen
A defense research agency is an organization that conducts scientific and technological research to develop advanced capabilities, systems, and knowledge in support of national security and military objectives.
-
B.
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.
-
C.
U.S. Army research laboratory
The U.S. Army Research Laboratory is the Army’s primary scientific and engineering research organization, conducting foundational and applied research to develop advanced technologies that enhance the capabilities, effectiveness, and protection of U.S. soldiers.
-
D.
defence estate
A defence estate is the collective portfolio of land, buildings, infrastructure, and facilities owned, leased, or managed by a nation's defence organization to support military operations, training, administration, and logistics.
-
E.
defense company
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:35 p.m.