Triple
T35073532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Bennelong |
E1011946
|
entity |
| Predicate | electorsRecorded |
P180991
|
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 Bennelong, electorsRecorded, over 100000 electors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorsRecorded Context triple: [Division of Bennelong, electorsRecorded, over 100000 electors]
-
A.
hasElectorsAsOf
chosen
Indicates that a specified entity has a certain set or number of electors at a given point in time.
-
B.
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.
-
C.
hasElectorsFrom
Indicates that an entity possesses or is associated with electors originating from a specified source or group.
-
D.
electsAt
Indicates that an election or selection of someone or something to a position, role, or office occurs at a specific time or in a specific context.
-
E.
electoratesCalled
Indicates that specific electoral districts or constituencies are given particular names or designations.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.