Triple
T33649319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duncan |
E862046
|
entity |
| Predicate | appearsInMerchandise |
P79243
|
FINISHED |
| Object | model railway toys |
—
|
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: model railway toys | Statement: [Duncan, appearsInMerchandise, model railway toys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInMerchandise Context triple: [Duncan, appearsInMerchandise, model railway toys]
-
A.
usedInMerchandise
chosen
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
B.
fanMerchandiseAvailable
Indicates that merchandise related to a fan or fandom is available for purchase or acquisition.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
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.
-
E.
appearedInCommercialFor
Indicates that one entity was featured or took part in a commercial advertisement promoting 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:42 a.m.