Triple
T30436128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 11.0 |
E774315
|
entity |
| Predicate | addsEmojiCategory |
P169430
|
FINISHED |
| Object | smileys and people |
—
|
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: smileys and people | Statement: [Unicode 11.0, addsEmojiCategory, smileys and people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsEmojiCategory Context triple: [Unicode 11.0, addsEmojiCategory, smileys and people]
-
A.
addsEmoji
Indicates that one entity appends or includes an emoji in relation to another entity or piece of content.
-
B.
includesEmoji
Indicates that the related content contains at least one emoji character.
-
C.
addsEmojiCharactersCount
Indicates that an action or process increases the number of emoji characters present in some content or text.
-
D.
addsEmojiSequencesCount
Indicates that an entity increases the number of emoji sequences associated with another entity or context.
-
E.
settingCategory
Indicates the classification or type of context in which something is set or configured (e.g., grouping settings under a common category).
- 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_69f68694ff888190b85abd31df01a71c |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:07 p.m.