Triple
T1083617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APS Divisions |
E24002
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational unit type |
C694
|
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 unit type Context triple: [APS Divisions, instanceOf, organizational unit type]
-
A.
organizational unit of IEEE
An organizational unit of IEEE is a formally recognized group within the IEEE structure, such as a society, council, region, section, chapter, or committee, that carries out specific professional, technical, or administrative functions in support of IEEE’s mission.
-
B.
organization
chosen
An organization is a structured group of people and resources coordinated to achieve shared goals or perform specific functions.
-
C.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
D.
intelligence organization unit
An intelligence organization unit is a structured group within an intelligence agency responsible for collecting, analyzing, and disseminating information to support decision-making and security objectives.
-
E.
organizational unit of the U.S. Securities and Exchange Commission
An organizational unit of the U.S. Securities and Exchange Commission is a distinct internal division, office, or program area with defined responsibilities, authority, and resources for carrying out specific aspects of the SEC’s regulatory, enforcement, or administrative mission.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:42 p.m.