Triple
T20108478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonavista—Burin—Trinity |
E490259
|
entity |
| Predicate | hasElectorsDataYear |
P52032
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Bonavista—Burin—Trinity, hasElectorsDataYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectorsDataYear Context triple: [Bonavista—Burin—Trinity, hasElectorsDataYear, 2015]
-
A.
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.
-
B.
hasElectorsFrom
Indicates that an entity possesses or is associated with electors originating from a specified source or group.
-
C.
appliesToElectionYear
chosen
Indicates that something is relevant, valid, or in effect specifically for a given election year.
-
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.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666ddb09881909ad2aedd1e8a78da |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:28 p.m.