Triple
T15818217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Dining Plan |
E383533
|
entity |
| Predicate | purchaseTiming |
P120195
|
FINISHED |
| Object | before arrival |
—
|
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: before arrival | Statement: [Disney Dining Plan, purchaseTiming, before arrival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purchaseTiming Context triple: [Disney Dining Plan, purchaseTiming, before arrival]
-
A.
purchaseContext
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
-
B.
purchaseFunctionEndDate
Indicates the date on which a purchase-related function, service, or entitlement comes to an end.
-
C.
purchaseMethod
Indicates the way or channel through which a purchase is made (e.g., online, in-store, by phone, or via a specific payment or ordering method).
-
D.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
E.
buys
Indicates that one entity purchases or acquires something from another entity, typically in exchange for money or other compensation.
- F. None of above. chosen
Provenance (4 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a552008190863343c9d41ebf3f |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:49 a.m.