Triple
T6559206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Senate |
E152531
|
entity |
| Predicate | committeeTypes |
P4423
|
FINISHED |
| Object | standing committees |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: standing committees | Statement: [Australian Senate, committeeTypes, standing committees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: committeeTypes Context triple: [Australian Senate, committeeTypes, standing committees]
-
A.
committeeSystem
Indicates that an entity operates under, is governed by, or is organized according to a committee-based decision-making system.
-
B.
hasCommitteeType
chosen
Indicates that an entity is associated with a committee of a specified type or classification.
-
C.
committeeInvolved
Indicates that a committee participates in, contributes to, or is otherwise actively involved in a particular activity, decision, or process.
-
D.
councilType
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
E.
committeeMember
Indicates that an entity serves as a member of a particular committee.
- F. None of above.
Provenance (3 batches)
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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.