Triple
T37642026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Data Analysis Branch |
E936639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mapping organization unit |
C62554
|
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: mapping organization unit Context triple: [Resource Data Analysis Branch, instanceOf, mapping organization unit]
-
A.
organizational unit designation
An organizational unit designation is a label or identifier that specifies a distinct division, department, or functional group within an organization’s structure.
-
B.
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.
-
C.
Verwaltungseinheit
Eine Verwaltungseinheit ist eine organisatorische Einheit innerhalb einer öffentlichen oder privaten Institution, die für die Erfüllung bestimmter Verwaltungsaufgaben und die Umsetzung von Richtlinien in einem abgegrenzten Zuständigkeitsbereich verantwortlich ist.
-
D.
healthcare organization unit
A healthcare organization unit is a distinct administrative or functional division within a healthcare system (such as a department, clinic, or ward) that delivers specific health-related services, manages resources, and supports patient care processes.
-
E.
intergovernmental organization unit
An intergovernmental organization unit is a structural subdivision within an intergovernmental organization that carries out specific functions, programs, or administrative responsibilities on behalf of its member states.
- F. None of above. chosen
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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.