Triple
T21626623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Hinkler |
E533720
|
entity |
| Predicate | electorsApproximateRange |
P145274
|
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: [Division of Hinkler, electorsApproximateRange, over 100000 electors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorsApproximateRange Context triple: [Division of Hinkler, electorsApproximateRange, over 100000 electors]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
approximateNumberOfVotersBefore
Indicates that one value represents an estimated count of voters that existed prior to a specified point in time or event.
-
C.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
D.
lapCountApproximate
Indicates that the recorded number of laps is an estimate rather than an exact, precise count.
-
E.
hasApproximateNumberOfResponsa
Indicates that an entity is associated with a rough or estimated count of responsa, rather than an exact number.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52131f2c8190b9966adf43a0fe4f |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:34 p.m.