Triple
T1247950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authorization for Use of Military Force Against Iraq Resolution of 2002 |
E26808
|
entity |
| Predicate | houseVoteTallyFor |
P8455
|
FINISHED |
| Object | 296 |
—
|
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: 296 | Statement: [Authorization for Use of Military Force Against Iraq Resolution of 2002, houseVoteTallyFor, 296]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseVoteTallyFor Context triple: [Authorization for Use of Military Force Against Iraq Resolution of 2002, houseVoteTallyFor, 296]
-
A.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
B.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
-
C.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
D.
totalVotesCast
chosen
Indicates the total number of votes that have been cast in a given election or voting event.
-
E.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf827e088190a16d845cea14f2c9 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.