Triple
T27810166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipwreck Shore |
E702495
|
entity |
| Predicate | queueRequirement |
P102279
|
FINISHED |
| Object | no ride queue required |
—
|
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: no ride queue required | Statement: [Shipwreck Shore, queueRequirement, no ride queue required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueRequirement Context triple: [Shipwreck Shore, queueRequirement, no ride queue required]
-
A.
hasQueueRequirement
chosen
Indicates that an entity must satisfy or adhere to a specified queue-related condition or rule.
-
B.
queueType
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
C.
queueTypical
Indicates that an entity is in or follows a standard or commonly expected queueing order or behavior relative to others.
-
D.
queueBehavior
Indicates how an entity manages or responds to items or events in a queue, such as their order, timing, or handling strategy.
-
E.
queueInterface
Indicates that one entity serves as a queue interface through which another entity can enqueue, dequeue, or otherwise manage queued items or requests.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6383da0e08190a4e394aba4b49348 |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:41 p.m.