Triple
T34504662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplemental Symbols and Pictographs |
E885848
|
entity |
| Predicate | isRelatedBlock |
P26441
|
FINISHED |
| Object | Emoticons |
—
|
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: Emoticons | Statement: [Supplemental Symbols and Pictographs, isRelatedBlock, Emoticons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedBlock Context triple: [Supplemental Symbols and Pictographs, isRelatedBlock, Emoticons]
-
A.
relatedBlock
chosen
Indicates that one block is associated with or connected to another block in some relevant way.
-
B.
belongsToBlock
Indicates that something is a member or component of a specific block or grouping.
-
C.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
-
D.
isRelatedUnit
Indicates that one unit has a defined relationship or association with another unit within a given system or context.
-
E.
isRelatedRouteOf
Indicates that one route is connected to, associated with, or serves as an alternative or complementary path to another route.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.