Triple
T3590527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plain (La Plaine) |
E76013
|
entity |
| Predicate | votingBehavior |
P42210
|
FINISHED |
| Object | often decisive in close votes |
—
|
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: often decisive in close votes | Statement: [Plain (La Plaine), votingBehavior, often decisive in close votes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingBehavior Context triple: [Plain (La Plaine), votingBehavior, often decisive in close votes]
-
A.
votingIs
chosen
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
B.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
C.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
D.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
E.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1581278819081dd73b4c71e422e |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.