Triple
T36783247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spida |
E908829
|
entity |
| Predicate | hasFanMerchandise |
P166310
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Spida, hasFanMerchandise, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanMerchandise Context triple: [Spida, hasFanMerchandise, yes]
-
A.
fanMerchandiseAvailable
chosen
Indicates that merchandise related to a fan or fandom is available for purchase or acquisition.
-
B.
hasMerchandiseTieIn
Indicates that one entity has a commercial or promotional product or line (merchandise) that is directly tied to, branded with, or derived from another entity.
-
C.
usedInMerchandise
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
D.
hasExtensiveMerchandise
Indicates that an entity offers a large and varied range of merchandise or products.
-
E.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:12 p.m.