Triple
T31445602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shops at Epcot |
E802178
|
entity |
| Predicate | primaryMerchandise |
P7216
|
FINISHED |
| Object | Disney character merchandise |
—
|
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: Disney character merchandise | Statement: [Shops at Epcot, primaryMerchandise, Disney character merchandise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMerchandise Context triple: [Shops at Epcot, primaryMerchandise, Disney character merchandise]
-
A.
primaryProduct
chosen
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
B.
merchandiseSource
Indicates that one entity is the origin, supplier, or provider from which another entity’s merchandise is obtained.
-
C.
secondaryProducts
Indicates that certain entities arise as secondary or byproduct outputs from a primary process, activity, or production.
-
D.
primaryAsset
Indicates that one entity is the main or most important asset associated with another entity.
-
E.
merchandiseRole
Indicates the specific functional role or purpose that a piece of merchandise serves within a commercial or retail context.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:09 p.m.