Triple
T20797844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Standard version 6.0 |
E511957
|
entity |
| Predicate | addsSymbolSet |
P141575
|
FINISHED |
| Object | Emoji symbols |
—
|
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: Emoji symbols | Statement: [Unicode Standard version 6.0, addsSymbolSet, Emoji symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsSymbolSet Context triple: [Unicode Standard version 6.0, addsSymbolSet, Emoji symbols]
-
A.
partOfSymbolSet
Indicates that one symbol belongs to, or is included within, a particular set of symbols.
-
B.
definesSymbol
Indicates that one entity specifies or establishes another entity as a symbol representing some concept, value, or object.
-
C.
registerSet
Indicates that an entity is assigned to or included within a particular register or set of registers.
-
D.
symbolicallyExtends
Indicates that one entity conceptually builds upon, generalizes, or inherits the structure or meaning of another in an abstract or symbolic way.
-
E.
regulatesSymbol
Indicates that one entity exercises control or governance over the use, meaning, or presentation of another entity’s symbol.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ae2c4c819087f620df31dc1aba |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:39 p.m.