Triple
T19276848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 5.2 |
E482078
|
entity |
| Predicate | hasPropertyUpdates |
P4061
|
FINISHED |
| Object | character properties |
—
|
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: character properties | Statement: [Unicode 5.2, hasPropertyUpdates, character properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyUpdates Context triple: [Unicode 5.2, hasPropertyUpdates, character properties]
-
A.
hasUpdatedElement
Indicates that an element has been modified or replaced with a more recent version within a given context or system.
-
B.
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.
-
C.
hasPhysicalPropertyChange
Indicates that an entity undergoes a modification in one of its physical properties, such as state, shape, or measurable characteristics.
-
D.
hasKeyChanges
Indicates that one entity undergoes or contains changes in musical key relative to another entity or version.
-
E.
hasUpdatePolicy
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbd5f34819086535f28fd880411 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.