Triple
T9485265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maelstrom |
E228743
|
entity |
| Predicate | fastpassAvailable |
P35685
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maelstrom, fastpassAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastpassAvailable Context triple: [Maelstrom, fastpassAvailable, yes]
-
A.
fastpassPlusAvailable
chosen
Indicates that a FastPass+ reservation or access option is available for the associated experience or service.
-
B.
hasFastPassHistory
Indicates that an entity has a record of previously obtaining or using a FastPass or similar priority-access privilege.
-
C.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
D.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
E.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804fb2b4819084c7f5a842dbe5a6 |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.