Triple
T1240112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authorization for Use of Military Force of 2001 |
E26637
|
entity |
| Predicate | proposedActionOn |
P21476
|
FINISHED |
| Object | repeal |
—
|
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: repeal | Statement: [Authorization for Use of Military Force of 2001, proposedActionOn, repeal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedActionOn Context triple: [Authorization for Use of Military Force of 2001, proposedActionOn, repeal]
-
A.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
C.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
D.
proposedAmendment
chosen
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
E.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf41c5d08190b07adbdb24d35a76 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.