Triple
T21336003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix (amusement attraction) |
E526047
|
entity |
| Predicate | commonMerchandise |
P53553
|
FINISHED |
| Object | phoenix-themed souvenirs |
—
|
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: phoenix-themed souvenirs | Statement: [Phoenix (amusement attraction), commonMerchandise, phoenix-themed souvenirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMerchandise Context triple: [Phoenix (amusement attraction), commonMerchandise, phoenix-themed souvenirs]
-
A.
merchandiseSource
Indicates that one entity is the origin, supplier, or provider from which another entity’s merchandise is obtained.
-
B.
merchandiseChange
Indicates a change in the type, quantity, or status of merchandise associated with an entity or transaction.
-
C.
usedInMerchandise
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
D.
typicalGoodsSold
chosen
Indicates the kinds of goods or products that an entity most commonly or characteristically sells.
-
E.
marketedProducts
Indicates that an entity promotes, sells, or otherwise brings specific products to market.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e898d7d8b88190b2f346e4592b3bc5 |
completed | April 22, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:43 p.m.