Triple
T756543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postal Regulatory Commission |
E15568
|
entity |
| Predicate | canAdjudicate |
P19254
|
FINISHED |
| Object | postal-related complaints |
—
|
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-related complaints | Statement: [Postal Regulatory Commission, canAdjudicate, postal-related complaints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAdjudicate Context triple: [Postal Regulatory Commission, canAdjudicate, postal-related complaints]
-
A.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
B.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
C.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canReview
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66ab4608190afcd81e6606c5116 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a62b497081909503c8d30c7ce1db |
completed | March 1, 2026, 8:48 p.m. |
Created at: March 1, 2026, 7:37 p.m.