Triple
T8154445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teddy |
E190410
|
entity |
| Predicate | isMerchandisedAs |
P79243
|
FINISHED |
| Object | Toy |
—
|
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: Toy | Statement: [Teddy, isMerchandisedAs, Toy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMerchandisedAs Context triple: [Teddy, isMerchandisedAs, Toy]
-
A.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
B.
usedInMerchandise
chosen
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
C.
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.
-
D.
isSoldIn
Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
-
E.
usedInECommerce
Indicates that something is employed or applied within the context of electronic commerce activities or systems.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d566b08190a6bb672f9c368806 |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.