Triple
T4752799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 IIHF World Championship |
E105515
|
entity |
| Predicate | officialHashtag |
P9354
|
FINISHED |
| Object | #IIHFWorlds |
—
|
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: #IIHFWorlds | Statement: [2019 IIHF World Championship, officialHashtag, #IIHFWorlds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialHashtag Context triple: [2019 IIHF World Championship, officialHashtag, #IIHFWorlds]
-
A.
hashtag
chosen
Indicates that an entity is associated with or labeled by a specific hashtag, typically used for categorization or topic tagging.
-
B.
socialMediaPlatformAssociatedWith
Indicates that there is an association or linkage between an entity and a specific social media platform.
-
C.
twitterHandle
Indicates that one entity is the Twitter username or account identifier associated with another entity.
-
D.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
E.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e5fba88190b1f28d1b0eed3f8e |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.