Triple
T1257173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USA FREEDOM Act |
E12419
|
entity |
| Predicate | passedHouseVote |
P24940
|
FINISHED |
| Object | 338-88 |
—
|
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: 338-88 | Statement: [USA FREEDOM Act, passedHouseVote, 338-88]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passedHouseVote Context triple: [USA FREEDOM Act, passedHouseVote, 338-88]
-
A.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
B.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
C.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
D.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
E.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfa8cfa08190ac49c437a94a843c |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc4a1f048190bd1ddcc4cc3fe057 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:50 p.m.