Triple
T4119546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postal Accountability and Enhancement Act |
E90376
|
entity |
| Predicate | renames |
P3432
|
FINISHED |
| Object | Postal Rate Commission to Postal Regulatory Commission |
—
|
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: Postal Rate Commission to Postal Regulatory Commission | Statement: [Postal Accountability and Enhancement Act, renames, Postal Rate Commission to Postal Regulatory Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renames Context triple: [Postal Accountability and Enhancement Act, renames, Postal Rate Commission to Postal Regulatory Commission]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
C.
reformName
Indicates that an entity has undergone a reform or change resulting in a new name or designation.
-
D.
renamedTo
chosen
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
E.
contextOfRenaming
Indicates the situational or historical context in which an entity’s name was or is being changed.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.