Triple
T1123808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUR |
E24672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizationalUnit |
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: organizationalUnit Context triple: [EUR, instanceOf, organizationalUnit]
-
A.
organization
chosen
An organization is a structured group of people and resources coordinated to achieve shared goals or perform specific functions.
-
B.
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.
-
C.
organizational unit of the United States Copyright Office
An organizational unit of the United States Copyright Office is a distinct internal division or office responsible for specific copyright-related functions, services, or administrative duties within the overall structure of the Copyright Office.
-
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.
administrative organ of an international organization
An administrative organ of an international organization is a permanent body responsible for managing the organization’s day-to-day operations, implementing its decisions, and providing support services to its other organs and member states.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:44 p.m.