Triple
T18563532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Technical Reports |
E453704
|
entity |
| Predicate | areUpdated |
P4061
|
FINISHED |
| Object | to track changes in 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: to track changes in the Unicode Standard | Statement: [Unicode Technical Reports, areUpdated, to track changes in the Unicode Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areUpdated Context triple: [Unicode Technical Reports, areUpdated, to track changes in the Unicode Standard]
-
A.
isUpdated
chosen
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
isUpdatedWhen
Indicates that one entity undergoes a change or refresh whenever another specified entity is modified or updated.
-
D.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
-
E.
updatedEvery
Indicates that something is refreshed or brought up to date at a regular, specified interval.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.