Triple
T15592814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Richmond |
E374786
|
entity |
| Predicate | electorateNumberOfElectors |
P16492
|
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 Richmond, electorateNumberOfElectors, over 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorateNumberOfElectors Context triple: [Division of Richmond, electorateNumberOfElectors, over 100000]
-
A.
numberOfElectors
chosen
Indicates the total count of electors associated with a given entity or context.
-
B.
electoralVoteFor
Indicates that a specified number of electoral votes are allocated or cast in favor of a particular candidate or option in an election.
-
C.
presidentialElectorAllocation
Indicates how presidential electors are distributed or assigned among different jurisdictions or candidates in an election.
-
D.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
E.
seatOfElector
Indicates the location or jurisdiction that serves as the official base or constituency of a given elector.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e5e43d48190a8fd367f13f1c7e1 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.