Triple
T12601694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petroleum and Petrochemicals |
E300872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Organizational unit |
C8231
|
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 Context triple: [Petroleum and Petrochemicals, instanceOf, Organizational unit]
-
A.
organizational unit category
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.
operational unit
chosen
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
-
C.
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.
-
D.
organizational unit of Microsoft
An organizational unit of Microsoft is a logical container within a directory service used to group and manage users, computers, and other resources under common administrative policies and controls.
-
E.
organizational unit at Google
An organizational unit at Google is a logical grouping of users, devices, and resources within the company’s directory structure used to apply and manage specific policies, settings, and access controls.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:09 p.m.