Triple
T19040351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel Hill Consensus Conference on Vasculitis Nomenclature |
E465983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | expert working group |
C38063
|
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: expert working group Context triple: [Chapel Hill Consensus Conference on Vasculitis Nomenclature, instanceOf, expert working group]
-
A.
technical expert group
A technical expert group is a team of specialized professionals convened to provide in-depth technical analysis, guidance, and recommendations on specific subject-matter issues.
-
B.
collaborative working group
A collaborative working group is a coordinated team of individuals who share responsibilities, knowledge, and decision-making to achieve a common goal or complete a specific project.
-
C.
international expert committee
An international expert committee is a formally organized group of specialists from multiple countries who collaboratively provide authoritative analysis, guidance, and recommendations on complex global issues within a specific domain.
-
D.
specialized group
chosen
A specialized group is a collection of individuals organized around a specific expertise, function, or shared interest to achieve focused goals or perform distinct tasks.
-
E.
intergovernmental working group
An intergovernmental working group is a collaborative body composed of representatives from multiple governments tasked with developing, coordinating, or advising on policies, standards, or actions in a specific issue area.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.