Triple
T35744691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hume |
E1033137
|
entity |
| Predicate | federalElectorateNumberOfVoters |
P128148
|
FINISHED |
| Object | over 100000 electors |
—
|
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 electors | Statement: [Hume, federalElectorateNumberOfVoters, over 100000 electors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalElectorateNumberOfVoters Context triple: [Hume, federalElectorateNumberOfVoters, over 100000 electors]
-
A.
federalElectorateOf
Indicates that one entity is the federal electoral district to which the other entity (such as a location or representative) belongs or is assigned.
-
B.
numberOfVoters
Indicates the total count of individuals who participated in a particular vote or election.
-
C.
votingPopulation
chosen
Indicates that the subject entity has a population of individuals who are eligible and/or registered to vote in elections associated with the object entity.
-
D.
numberOfElectorates
Indicates the total count of electoral districts or constituencies associated with a given entity.
-
E.
electorateNumber
Indicates the numerical identifier assigned to a specific electorate or voting district within an electoral system.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a16df2808190bd9dc510537b7fbf |
completed | May 3, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.