Triple
T29728526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau National Interprofessionnel de l’Armagnac |
E752253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interprofessional bureau |
C56129
|
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: interprofessional bureau Context triple: [Bureau National Interprofessionnel de l’Armagnac, instanceOf, interprofessional bureau]
-
A.
interagency group
An interagency group is a collaborative body composed of representatives from multiple government agencies that coordinates policies, resources, and actions on shared issues or objectives.
-
B.
interagency committee
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
-
C.
intergovernmental board
An intergovernmental board is a formal decision-making body composed of representatives from multiple governments that coordinates policies, oversees joint initiatives, and manages shared responsibilities across participating states.
-
D.
interstate agency
An interstate agency is an organization formed by two or more states through a formal agreement to collaboratively manage shared resources, services, or regulatory responsibilities across their borders.
-
E.
interdisciplinary hub
An interdisciplinary hub is a collaborative space—physical or virtual—where experts from diverse fields converge to share knowledge, integrate methods, and co-create innovative solutions to complex problems.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:40 p.m.