Triple
T3434872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noosa Shire |
E72424
|
entity |
| Predicate | re-establishedAsLGA |
P9113
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Noosa Shire, re-establishedAsLGA, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-establishedAsLGA Context triple: [Noosa Shire, re-establishedAsLGA, 2014]
-
A.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
B.
redistrictedFrom
Indicates that one political or administrative district has been created, altered, or derived from another through a redistricting process.
-
C.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
D.
redistrictedBy
Indicates that an entity’s boundaries or districts have been altered or redefined by another specified agent or authority.
-
E.
reincorporated
Indicates that an entity has been formed again or brought back into existence as a corporation after having previously ceased or changed its corporate status.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9c3300881909f5c3544f8923b41 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.