Triple
T27852549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of McEwen |
E703994
|
entity |
| Predicate | isNamedElectorate |
P164538
|
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: [Division of McEwen, isNamedElectorate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedElectorate Context triple: [Division of McEwen, isNamedElectorate, true]
-
A.
isRemoteElectorate
Indicates that an electorate is classified as geographically remote or distant from major population centers.
-
B.
electorateIncludes
Indicates that a particular electorate or voting body contains or encompasses the specified member or group as part of those entitled to participate.
-
C.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
-
D.
hasParliamentaryElectorate
Indicates that a political or administrative entity is represented by, or belongs to, a specific parliamentary electoral district.
-
E.
heldInElectorate
Indicates that an event, such as an election or vote, takes place within the geographic boundaries of a specific electorate.
- F. None of above. chosen
Provenance (4 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 6:11 p.m.