Triple
T9576577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Track pavilion |
E231059
|
entity |
| Predicate | usesFastpassOrSuccessor |
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: [Test Track pavilion, usesFastpassOrSuccessor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFastpassOrSuccessor Context triple: [Test Track pavilion, usesFastpassOrSuccessor, yes]
-
A.
hasFastPassHistory
Indicates that an entity has a record of previously obtaining or using a FastPass or similar priority-access privilege.
-
B.
fastpassPlusAvailable
chosen
Indicates that a FastPass+ reservation or access option is available for the associated experience or service.
-
C.
hasTouristQueue
Indicates that there is a designated queue or waiting line specifically for tourists in relation to a place, service, or attraction.
-
D.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
E.
hasReservationSystem
Indicates that an entity uses or is equipped with a system for managing reservations or bookings.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ac17a48190bb8448394f22b1e9 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.