Triple
T26091547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Mayo |
E658136
|
entity |
| Predicate | electorsApprox |
P76499
|
FINISHED |
| Object | over 100000 |
—
|
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: over 100000 | Statement: [Division of Mayo, electorsApprox, over 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorsApprox Context triple: [Division of Mayo, electorsApprox, over 100000]
-
A.
hasElectorsFrom
Indicates that an entity possesses or is associated with electors originating from a specified source or group.
-
B.
electorateApprox
chosen
Indicates an approximate or estimated size or value of an electorate associated with an entity.
-
C.
electorsApproximateRange
Indicates that one entity specifies an estimated or approximate numerical range for the number of electors associated with another entity.
-
D.
electorsAppointedBy
Indicates that one party is responsible for officially selecting or designating the electors who will act or vote on behalf of another entity.
-
E.
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.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 26, 2026, 7:47 p.m.