Triple
T15818220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Dining Plan |
E383533
|
entity |
| Predicate | creditTracking |
P60544
|
FINISHED |
| Object | linked to guest’s resort reservation |
—
|
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: linked to guest’s resort reservation | Statement: [Disney Dining Plan, creditTracking, linked to guest’s resort reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditTracking Context triple: [Disney Dining Plan, creditTracking, linked to guest’s resort reservation]
-
A.
creditRecognition
Indicates that one party formally acknowledges and accepts academic or professional credits earned from another source.
-
B.
creditFunction
Indicates a financial role or operation through which an entity extends, manages, or utilizes credit within an economic or transactional context.
-
C.
creditsCanBe
Indicates that certain credits are permitted to be in a specified state, category, or usage condition.
-
D.
creditSchedule
Indicates a planned or agreed-upon timetable for extending, using, or repaying credit between parties.
-
E.
dataTracked
chosen
Indicates that information about an entity or interaction is being collected, recorded, or monitored over time.
- 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_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. |
Created at: April 10, 2026, 4:49 a.m.