Triple
T11080886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Assembly of Western Australia |
E261987
|
entity |
| Predicate | hasFixedTerms |
P34433
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Legislative Assembly of Western Australia, hasFixedTerms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedTerms Context triple: [Legislative Assembly of Western Australia, hasFixedTerms, true]
-
A.
termFixedBy
Indicates that a term is determined, constrained, or made unchangeable by another entity or condition.
-
B.
hasNoFixedTermLength
chosen
Indicates that the relationship or agreement exists without a predetermined or fixed duration for how long it will remain in effect.
-
C.
hasStaggeredTerms
Indicates that the members or positions within a body or group serve overlapping terms that begin and end at different times rather than all simultaneously.
-
D.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
E.
hasNumberOfTerms
Indicates the quantity of distinct terms or elements associated with a given entity or expression.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79996d9408190b159d14b23c25ed1 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.