Triple
T12102686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἡλιαία |
E288227
|
entity |
| Predicate | votingInstruments |
P94632
|
FINISHED |
| Object | voting tokens (psephoi) |
—
|
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: voting tokens (psephoi) | Statement: [Ἡλιαία, votingInstruments, voting tokens (psephoi)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingInstruments Context triple: [Ἡλιαία, votingInstruments, voting tokens (psephoi)]
-
A.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
B.
typeOfVoting
chosen
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
-
C.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
D.
electionSystemFeature
Indicates that an election system possesses a specific characteristic, mechanism, or procedural feature related to how elections are conducted or managed.
-
E.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.