Triple
T4802158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenner |
E106858
|
entity |
| Predicate | hasPrepollVoting |
P60213
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fenner, hasPrepollVoting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrepollVoting Context triple: [Fenner, hasPrepollVoting, yes]
-
A.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
-
B.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
C.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
D.
hasByElections
Indicates that one entity conducts, experiences, or is associated with one or more by-elections in relation to another contextual entity (such as a jurisdiction, office, or time period).
-
E.
approximateNumberOfVotersBefore
Indicates that one value represents an estimated count of voters that existed prior to a specified point in time or event.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:23 p.m.