Triple
T1254087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meetings Committee |
E26945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized committee of the Society of Rheology |
C1099
|
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: specialized committee of the Society of Rheology Context triple: [Meetings Committee, instanceOf, specialized committee of the Society of Rheology]
-
A.
scientific committee
A scientific committee is a group of experts who collaboratively evaluate, guide, and make decisions on scientific matters, such as research quality, funding, ethics, and strategic priorities.
-
B.
research committee
chosen
A research committee is a group of appointed individuals responsible for evaluating, guiding, and overseeing research activities, proposals, and policies within an organization or institution.
-
C.
scholarly committee
A scholarly committee is a group of experts convened to evaluate, guide, and make decisions on academic matters such as research quality, curriculum, or institutional policies.
-
D.
division of a scientific society
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
-
E.
unit of the American Physical Society
A unit of the American Physical Society is a subdivision of the organization, such as a division, topical group, forum, or section, that focuses on a specific area of physics or professional interest to support research, communication, and community-building among its members.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.