Triple
T9602486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Call |
E231881
|
entity |
| Predicate | typicalMerchandiseSource |
P49828
|
FINISHED |
| Object | past-season inventory |
—
|
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: past-season inventory | Statement: [Last Call, typicalMerchandiseSource, past-season inventory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMerchandiseSource Context triple: [Last Call, typicalMerchandiseSource, past-season inventory]
-
A.
usedInMerchandise
Indicates that something (such as a work, character, or design) is utilized or featured as part of a merchandise item.
-
B.
brandSource
chosen
Indicates that one entity is the originating or providing brand associated with another entity (such as a product, service, or content).
-
C.
typicalGoodsSold
Indicates the kinds of goods or products that an entity most commonly or characteristically sells.
-
D.
tradeMedium
Indicates that one entity serves as the medium or instrument through which another entity conducts trade or exchange transactions.
-
E.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5af8f0819089408ed630afa812 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.