Triple
T9484671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Living with the Land |
E228727
|
entity |
| Predicate | fastpassStatus |
P81367
|
FINISHED |
| Object | formerly offered 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 FastPass+ | Statement: [Living with the Land, fastpassStatus, formerly offered FastPass+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastpassStatus Context triple: [Living with the Land, fastpassStatus, formerly offered FastPass+]
-
A.
fastpassPlusAvailable
Indicates that a FastPass+ reservation or access option is available for the associated experience or service.
-
B.
hasFastPassHistory
chosen
Indicates that an entity has a record of previously obtaining or using a FastPass or similar priority-access privilege.
-
C.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
D.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
E.
fareStatus
Indicates the current condition or classification of a fare within a pricing or ticketing context (e.g., available, restricted, or expired).
- 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_69cd804e278c8190b1f869158075cd52 |
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.