Triple
T31445208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Living with the Land |
E802167
|
entity |
| Predicate | fastPassHistory |
P81367
|
FINISHED |
| Object | previously offered FastPass+ access |
—
|
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: previously offered FastPass+ access | Statement: [Living with the Land, fastPassHistory, previously offered FastPass+ access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastPassHistory Context triple: [Living with the Land, fastPassHistory, previously offered FastPass+ access]
-
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.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
E.
fareSystemPreviously
Indicates that a particular fare system existed or was in use at an earlier time relative to another fare system or time period.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:08 p.m.