Triple
T6405381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R. 2048 |
E144164
|
entity |
| Predicate | replacesProgram |
P53586
|
FINISHED |
| Object | NSA bulk telephony metadata program under Section 215 |
—
|
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: NSA bulk telephony metadata program under Section 215 | Statement: [H.R. 2048, replacesProgram, NSA bulk telephony metadata program under Section 215]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesProgram Context triple: [H.R. 2048, replacesProgram, NSA bulk telephony metadata program under Section 215]
-
A.
replacedProgramme
chosen
Indicates that one programme has been superseded or taken the place of another programme.
-
B.
replacedProcess
Indicates that one process has been substituted or superseded by another process.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
formerProgram
Indicates that an entity previously held the role or status of a program but no longer does so.
-
E.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068b22c74819092228010708aec6b |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.