Triple
T37063275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Election Commission members |
E917376
|
entity |
| Predicate | mayAdjudicate |
P19254
|
FINISHED |
| Object | electoral disputes |
—
|
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: electoral disputes | Statement: [Election Commission members, mayAdjudicate, electoral disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAdjudicate Context triple: [Election Commission members, mayAdjudicate, electoral disputes]
-
A.
canAdjudicate
chosen
Indicates that an entity has the authority or capacity to formally judge, decide, or resolve a dispute, case, or issue involving another entity or matter.
-
B.
mayAdmit
Indicates that one entity has the permission or authority to allow another entity to enter, join, or be accepted into something.
-
C.
mayApprove
Indicates that an entity has the authority or permission to approve another entity or action, but is not required to do so.
-
D.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
E.
adjudicationType
Indicates the specific kind or category of formal judgment or decision rendered in a legal or administrative adjudication 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.