Triple
T8049996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration of war on Japan |
E187648
|
entity |
| Predicate | voteResultInHouse |
P10095
|
FINISHED |
| Object | 388–1 |
—
|
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: 388–1 | Statement: [Declaration of war on Japan, voteResultInHouse, 388–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteResultInHouse Context triple: [Declaration of war on Japan, voteResultInHouse, 388–1]
-
A.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
C.
passedHouseVote
Indicates that a proposed measure or bill has received sufficient affirmative votes to be approved by the House of Representatives.
-
D.
senateVoteTallyFor
Indicates the recorded vote count or outcome in the senate for a particular measure, motion, or item.
-
E.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7826288190b2f292a7d34fcd80 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.