Triple
T37226491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Cat and Jerry Mouse |
E923016
|
entity |
| Predicate | merchandisedAs |
P79243
|
FINISHED |
| Object | 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: toys | Statement: [Tom Cat and Jerry Mouse, merchandisedAs, toys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: merchandisedAs Context triple: [Tom Cat and Jerry Mouse, merchandisedAs, toys]
-
A.
merchandiseSource
Indicates that one entity is the origin, supplier, or provider from which another entity’s merchandise is obtained.
-
B.
merchandiseRole
Indicates the specific functional role or purpose that a piece of merchandise serves within a commercial or retail context.
-
C.
usedInMerchandise
chosen
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
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.
merchandisingPartner
Indicates a relationship where one party collaborates with another to plan, manage, or execute the promotion, display, or sale of products or services.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.