Triple
T5689862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Tonkin Resolution |
E125401
|
entity |
| Predicate | datePassedSenate |
P10398
|
FINISHED |
| Object | 1964-08-07 |
—
|
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: 1964-08-07 | Statement: [Gulf of Tonkin Resolution, datePassedSenate, 1964-08-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePassedSenate Context triple: [Gulf of Tonkin Resolution, datePassedSenate, 1964-08-07]
-
A.
senatePassageDate
chosen
Indicates the date on which a senate formally passed or approved a specific measure, bill, or action.
-
B.
dateOfFinalSenateVotes
Indicates the calendar date on which the final voting session occurred in the Senate for a given measure or action.
-
C.
passedHouseDate
Indicates the date on which a proposed measure or item was approved or passed by the House.
-
D.
adviceAndConsentFor
Indicates that one party formally reviews, approves, or rejects a proposed action or decision initiated by another party, typically as a required check before it can take effect.
-
E.
passedHouseVote
Indicates that a proposed measure or bill has received sufficient affirmative votes to be approved by the House of Representatives.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.