Triple
T14463315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diribitorium |
E358639
|
entity |
| Predicate | typeOfElectoralActivity |
P31563
|
FINISHED |
| Object | vote counting |
—
|
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: vote counting | Statement: [Diribitorium, typeOfElectoralActivity, vote counting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfElectoralActivity Context triple: [Diribitorium, typeOfElectoralActivity, vote counting]
-
A.
electoralActivity
Indicates involvement in activities related to organizing, participating in, or influencing an election or electoral process.
-
B.
genreOfPoliticalActivity
chosen
Indicates the specific type or category of political activity that characterizes or classifies a given political action or engagement.
-
C.
electionParticipatedIn
Indicates that an entity took part as a candidate, voter, organizer, or in another official capacity in a specific election.
-
D.
postPoliticalActivity
Indicates that an entity engages in political actions or activities following a particular event, period, or condition.
-
E.
electoralNature
Indicates that something has the character, features, or conditions related to elections or the electoral process.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91ad67bc81908ecdaa7262f6dc55 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.