Triple
T15004963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Capricornia |
E377684
|
entity |
| Predicate | electors |
P16492
|
FINISHED |
| Object | about 110000 |
—
|
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: about 110000 | Statement: [Division of Capricornia, electors, about 110000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electors Context triple: [Division of Capricornia, electors, about 110000]
-
A.
elects
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
-
B.
electorsAppointedBy
Indicates that one party is responsible for officially selecting or designating the electors who will act or vote on behalf of another entity.
-
C.
electorsSequestered
Indicates that the electors are isolated or kept apart, typically to prevent outside influence during a decision-making or voting process.
-
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.
numberOfElectors
chosen
Indicates the total count of electors associated with a given entity or context.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7322b5c81909089cbbf816e1436 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.