Triple
T17078272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dixie cups and plates |
E414404
|
entity |
| Predicate | typicalPurchaseContext |
P97560
|
FINISHED |
| Object | party preparation |
—
|
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: party preparation | Statement: [Dixie cups and plates, typicalPurchaseContext, party preparation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPurchaseContext Context triple: [Dixie cups and plates, typicalPurchaseContext, party preparation]
-
A.
purchaseContext
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
-
B.
typicalCircumstance
Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
-
C.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
D.
orderPurpose
Indicates that an order is placed with the specific purpose or intended use of the ordered item or service.
-
E.
primaryConsumptionContext
chosen
Indicates the main situation, setting, or context in which something is typically used, consumed, or experienced.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe0e9cc8190b6c4b6065b474d1d |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.