Triple
T73740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technical Committee on Humanoid Robotics |
E1477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical committee |
C308
|
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: technical committee Context triple: [Technical Committee on Humanoid Robotics, instanceOf, technical committee]
-
A.
socio-technical system
A socio-technical system is an interconnected arrangement of people, technologies, and organizational structures whose interactions jointly shape how work is performed and outcomes are produced.
-
B.
United States Senate committee
A United States Senate committee is a specialized group of senators assigned to consider legislation, conduct hearings, and oversee federal agencies and programs within a particular policy area.
-
C.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
D.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
E.
intelligence oversight committee
An intelligence oversight committee is a formal body responsible for monitoring, reviewing, and regulating the activities of intelligence agencies to ensure legality, accountability, and alignment with democratic norms and national interests.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.