Triple
T7222267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electoral Commission (United States, 1877) |
E150286
|
entity |
| Predicate | methodOfDecision |
P35633
|
FINISHED |
| Object | majority vote |
—
|
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 vote | Statement: [Electoral Commission (United States, 1877), methodOfDecision, majority vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfDecision Context triple: [Electoral Commission (United States, 1877), methodOfDecision, majority vote]
-
A.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
B.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
C.
decisionStyle
Indicates the characteristic way an entity approaches, processes, and makes decisions in a given context.
-
D.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
E.
decisionMakingRule
chosen
Indicates the principle, guideline, or procedure that governs how a decision is made in a given context.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b42c5c81908c405f161c35ffb4 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.