Triple
T5796109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curiate Assembly |
E128511
|
entity |
| Predicate | voteDecisionRule |
P3460
|
FINISHED |
| Object | majority of curiae |
—
|
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: majority of curiae | Statement: [Curiate Assembly, voteDecisionRule, majority of curiae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteDecisionRule Context triple: [Curiate Assembly, voteDecisionRule, majority of curiae]
-
A.
voteRequirement
chosen
Indicates the minimum level or type of vote needed for a decision, action, or status to be valid or approved.
-
B.
presidingOfficerVoteRule
Indicates the rule or conditions under which the presiding officer is allowed or required to cast a vote in a decision-making process.
-
C.
voteSplit
Indicates that a voting outcome is divided among multiple options or parties rather than being unanimous or clearly majority.
-
D.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
E.
votePattern
Indicates a recurring way or tendency in how an entity casts votes across issues, candidates, or time.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.