Triple
T30436104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 11.0 |
E774315
|
entity |
| Predicate | standardizedVariantsAdded |
P180723
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Unicode 11.0, standardizedVariantsAdded, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedVariantsAdded Context triple: [Unicode 11.0, standardizedVariantsAdded, 2]
-
A.
extendedVariantUsedFor
Indicates that one entity is an extended or modified variant that is used in place of, or for the purposes of, another entity.
-
B.
modernizedVariants
Indicates that one entity is a modernized or updated form or version of another entity.
-
C.
previouslyStandardizedAs
Indicates that an entity was formerly standardized under a different name, code, or specification than the one it currently has.
-
D.
hasNonStandardizedVarieties
Indicates that an entity possesses forms or variants that are not governed by a uniform or officially established standard.
-
E.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
- F. None of above. chosen
Provenance (4 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 29, 2026, 8:07 p.m.