Triple
T1247923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authorization for Use of Military Force Against Iraq Resolution of 2002 |
E26808
|
entity |
| Predicate | datePassedByHouse |
P10397
|
FINISHED |
| Object | 2002-10-10 |
—
|
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: 2002-10-10 | Statement: [Authorization for Use of Military Force Against Iraq Resolution of 2002, datePassedByHouse, 2002-10-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePassedByHouse Context triple: [Authorization for Use of Military Force Against Iraq Resolution of 2002, datePassedByHouse, 2002-10-10]
-
A.
housePassageDate
chosen
Indicates the date on which a measure or item was passed or approved by a legislative house.
-
B.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
C.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
D.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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.