Triple
T5570912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DUCET |
E146196
|
entity |
| Predicate | updatedWith |
P4421
|
FINISHED |
| Object | new versions of the Unicode Standard |
—
|
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: new versions of the Unicode Standard | Statement: [DUCET, updatedWith, new versions of the Unicode Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedWith Context triple: [DUCET, updatedWith, new versions of the Unicode Standard]
-
A.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
B.
updated
chosen
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
updatesSpecificationOf
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
E.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020502a288190af37f9ebb88fccae |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.