Triple
T31758480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nominations and Appointments Committee of the Senate of the University of Sydney |
E810616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appointments committee |
C59138
|
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: appointments committee Context triple: [Nominations and Appointments Committee of the Senate of the University of Sydney, instanceOf, appointments committee]
-
A.
petitions committee
A petitions committee is a formal body, typically within a legislative or organizational structure, responsible for receiving, reviewing, and making recommendations or decisions on petitions submitted by individuals or groups.
-
B.
committee area
A committee area is a designated space or domain in which a specific committee operates, deliberates, and exercises its responsibilities or authority.
-
C.
conference committee
A conference committee is a group of individuals responsible for planning, organizing, and overseeing the academic, logistical, and promotional aspects of a conference.
-
D.
senior committee
A senior committee is a group of high-ranking or experienced individuals formally convened to provide oversight, strategic guidance, and key decisions on significant organizational matters.
-
E.
public accounts committee
A public accounts committee is a legislative body responsible for examining government expenditures to ensure they are lawful, efficient, and in line with approved budgets, thereby promoting transparency and accountability in public finance.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:30 p.m.