Triple
T27534968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright Patman Bonus Bill |
E695071
|
entity |
| Predicate | intendedToModify |
P12017
|
FINISHED |
| Object | Adjusted service certificates payment schedule |
—
|
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: Adjusted service certificates payment schedule | Statement: [Wright Patman Bonus Bill, intendedToModify, Adjusted service certificates payment schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedToModify Context triple: [Wright Patman Bonus Bill, intendedToModify, Adjusted service certificates payment schedule]
-
A.
mayBeModifiedBy
chosen
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
B.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
C.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
D.
intendedToMerge
Indicates that one entity had the purpose or plan to combine or consolidate with another entity into a single unit.
-
E.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 1:28 p.m.