Triple
T13106105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Acquisition Service business lines |
E310846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational unit grouping |
C9169
|
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 grouping Context triple: [Federal Acquisition Service business lines, instanceOf, organizational unit grouping]
-
A.
organizational unit category
chosen
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
-
B.
user group
A user group is a collection of users who share common permissions, roles, or characteristics within a system, enabling collective management and access control.
-
C.
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.
-
D.
organizational unit of the Library of Congress
An organizational unit of the Library of Congress is a distinct administrative division, such as a department, office, or service, responsible for specific functions that support the Library’s overall mission and operations.
-
E.
organization
An organization is a structured group of people and resources coordinated to achieve shared goals or perform specific functions.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:05 p.m.