Triple
T28377026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly River Run |
E718779
|
entity |
| Predicate | hasFastpassHistory |
P81367
|
FINISHED |
| Object | formerly offered Disney FASTPASS |
—
|
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: formerly offered Disney FASTPASS | Statement: [Grizzly River Run, hasFastpassHistory, formerly offered Disney FASTPASS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFastpassHistory Context triple: [Grizzly River Run, hasFastpassHistory, formerly offered Disney FASTPASS]
-
A.
hasFastPassHistory
chosen
Indicates that an entity has a record of previously obtaining or using a FastPass or similar priority-access privilege.
-
B.
fastpassPlusAvailable
Indicates that a FastPass+ reservation or access option is available for the associated experience or service.
-
C.
hasExpressPassAccess
Indicates that an entity is granted special expedited or priority access, typically bypassing standard queues or procedures.
-
D.
hasTourHistory
Indicates that an entity has a record of past tours or tour-related activities.
-
E.
hasTourHistoryWith
Indicates that two entities have previously participated together in one or more tours or touring events.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 1:03 a.m.