Triple
T6469934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCD |
E142321
|
entity |
| Predicate | updatedWithEach |
P25819
|
FINISHED |
| Object | new version 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 version of the Unicode Standard | Statement: [UCD, updatedWithEach, new version of the Unicode Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedWithEach Context triple: [UCD, updatedWithEach, new version of the Unicode Standard]
-
A.
updatedWithEachVersionOf
chosen
Indicates that something is modified or revised every time a new version of another entity is released.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
-
E.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a2e896481908ed004e3b0a33121 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.