Triple
T2553176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frappuccino blended beverages |
E56672
|
entity |
| Predicate | offeredSize |
P12465
|
FINISHED |
| Object | Tall |
—
|
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: Tall | Statement: [Frappuccino blended beverages, offeredSize, Tall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredSize Context triple: [Frappuccino blended beverages, offeredSize, Tall]
-
A.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
B.
includesSizeRange
chosen
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
C.
hasLotSize
Indicates that an entity possesses a specific amount or extent of physical area, typically referring to the size of a parcel of land or property lot.
-
D.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.