Triple
T36846072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuapeka |
E910549
|
entity |
| Predicate | electorateExistenceEnd |
P105292
|
FINISHED |
| Object | 1911 |
—
|
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: 1911 | Statement: [Tuapeka, electorateExistenceEnd, 1911]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorateExistenceEnd Context triple: [Tuapeka, electorateExistenceEnd, 1911]
-
A.
electorateUntil
chosen
Indicates that an entity serves as an electorate for another entity up to, but not beyond, a specified point in time.
-
B.
electorateEstablished
Indicates that an electorate or voting district has been formally created or brought into existence.
-
C.
parliamentaryTermEndEvent
Indicates the event or point in time at which a specific parliamentary term formally concludes.
-
D.
electorateStatus
Indicates the relationship between an individual and a political jurisdiction specifying whether, and in what capacity, they are eligible or registered to vote in its elections.
-
E.
electorateEstablishedFor
Indicates that a particular electorate or voting district has been created or designated to serve and represent a specific entity (such as a body, office, or jurisdiction).
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:13 p.m.