Triple
T6668521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 4.1 |
E151664
|
entity |
| Predicate | includesEmoji |
P72365
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Unicode 4.1, includesEmoji, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEmoji Context triple: [Unicode 4.1, includesEmoji, no]
-
A.
addsEmoji
Indicates that one entity appends or includes an emoji in relation to another entity or piece of content.
-
B.
addsEmojiCharactersCount
Indicates that an action or process increases the number of emoji characters present in some content or text.
-
C.
addsEmojiSequencesCount
Indicates that an entity increases the number of emoji sequences associated with another entity or context.
-
D.
supportsUnicode
Indicates that an entity is capable of correctly handling, storing, or displaying Unicode-encoded text.
-
E.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6ce72809c8190be85f6e42ca1c8ea |
completed | March 27, 2026, 6:37 p.m. |
Created at: March 27, 2026, 2:02 p.m.