Triple
T38253201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddisbury |
E1017709
|
entity |
| Predicate | hasElectorateApprox |
P76499
|
FINISHED |
| Object | 70000 |
—
|
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: 70000 | Statement: [Eddisbury, hasElectorateApprox, 70000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectorateApprox Context triple: [Eddisbury, hasElectorateApprox, 70000]
-
A.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
-
B.
isElectorateOf
Indicates that a group of eligible voters collectively has the right to vote in elections for a specified political body, office, or jurisdiction.
-
C.
hasElectorateProfile
Indicates that an entity is associated with a specific electorate-related profile describing its voting or demographic characteristics.
-
D.
hasElectors
Indicates that an entity is associated with one or more electors who have the authority to vote or make a selection on its behalf.
-
E.
electorateApprox
chosen
Indicates an approximate or estimated size or value of an electorate associated with an entity.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:30 p.m.