Triple
T26241180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Australia |
E656316
|
entity |
| Predicate | movesToPermanentSeatInYear |
P113197
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [High Court of Australia, movesToPermanentSeatInYear, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movesToPermanentSeatInYear Context triple: [High Court of Australia, movesToPermanentSeatInYear, 1980]
-
A.
movedToInYear
chosen
Indicates that an entity changed location or residence to a specified place in a particular year.
-
B.
movedSeatTo
Indicates that one entity changed another entity’s seating position from one place to another.
-
C.
permanentSeat
Indicates that an entity holds a seat or position that is intended to be ongoing and not subject to regular expiration, rotation, or reappointment.
-
D.
clubMoveYear
Indicates the year in which an entity changes or transfers its affiliation to a different club.
-
E.
movedSeatFrom
Indicates that an entity changed its seating position from a specified original seat or location to another.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8f7f9c8190bb8cb8f8ac4c0ca5 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:03 p.m.