Triple
T1241581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Character Database |
E26667
|
entity |
| Predicate | updatedWhen |
P6757
|
FINISHED |
| Object | new Unicode version is released |
—
|
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 Unicode version is released | Statement: [Unicode Character Database, updatedWhen, new Unicode version is released]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedWhen Context triple: [Unicode Character Database, updatedWhen, new Unicode version is released]
-
A.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
B.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
-
C.
updatedSpecificationDate
chosen
Indicates the date on which a specification was last revised or brought up to date.
-
D.
knownSince
Indicates the point in time from which one entity has been aware of, acquainted with, or in possession of knowledge about another entity.
-
E.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf44ac3c8190a28a333b320305fd |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.