Triple
T408269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate of Australia |
E9428
|
entity |
| Predicate | disputeResolutionMechanism |
P6659
|
FINISHED |
| Object | double dissolution |
—
|
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: double dissolution | Statement: [Senate of Australia, disputeResolutionMechanism, double dissolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeResolutionMechanism Context triple: [Senate of Australia, disputeResolutionMechanism, double dissolution]
-
A.
methodOfDisputeResolution
chosen
Indicates the process or mechanism used to settle a disagreement or conflict between parties.
-
B.
disputePolicy
Indicates that there is a formal disagreement or conflict regarding a policy, typically triggering procedures for review, negotiation, or resolution.
-
C.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
D.
handlesDisputesOver
Indicates that one entity is responsible for managing, resolving, or adjudicating disputes concerning another entity.
-
E.
negotiationForum
Indicates that a negotiation or bargaining process takes place within, or is facilitated by, a particular forum, venue, or platform.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbf0650819080753815ca280eec |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.