Triple
T22185998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribal Assembly |
E548297
|
entity |
| Predicate | votingProcedure |
P2726
|
FINISHED |
| Object | citizens vote within their tribe |
—
|
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: citizens vote within their tribe | Statement: [Tribal Assembly, votingProcedure, citizens vote within their tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingProcedure Context triple: [Tribal Assembly, votingProcedure, citizens vote within their tribe]
-
A.
votingMethod
chosen
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
B.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
C.
voteProcess
Indicates the formal procedure by which participants cast and record their votes to reach a decision or outcome.
-
D.
typeOfVoting
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
-
E.
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.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa8f178819094d1556df5aee5b9 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.