Triple
T6350893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of the Universal Postal Union |
E142866
|
entity |
| Predicate | areRevised |
P60216
|
FINISHED |
| Object | periodically by Universal Postal Union Congresses |
—
|
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: periodically by Universal Postal Union Congresses | Statement: [Acts of the Universal Postal Union, areRevised, periodically by Universal Postal Union Congresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRevised Context triple: [Acts of the Universal Postal Union, areRevised, periodically by Universal Postal Union Congresses]
-
A.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
B.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
-
C.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
D.
updatedIn
chosen
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
E.
isAmendmentTo
Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067dc2790819084aaf7067dc25733 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.