Triple
T24162916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo Awards administration subcommittee |
E598891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational subcommittee |
C30665
|
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: organizational subcommittee Context triple: [Hugo Awards administration subcommittee, instanceOf, organizational subcommittee]
-
A.
governing body subcommittee
A governing body subcommittee is a smaller, specialized group formed within a larger decision-making organization to focus on specific issues, conduct detailed analysis, and make recommendations or decisions within its defined scope.
-
B.
subcommittee of a United Nations committee
A subcommittee of a United Nations committee is a smaller, specialized body established under a parent UN committee to focus on specific issues, conduct detailed analysis, and make recommendations to support the committee’s broader mandate.
-
C.
Specialized committee
chosen
A specialized committee is a focused group of individuals formed within a larger organization to address, investigate, or manage specific issues, tasks, or areas of expertise.
-
D.
organizational committee
An organizational committee is a structured group of individuals formally appointed within an organization to plan, coordinate, and oversee specific functions, projects, or decision-making processes.
-
E.
subordinate organization
A subordinate organization is an entity that operates under the authority, control, or oversight of a higher-level organization, carrying out specific functions or responsibilities delegated to it.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:32 p.m.