Triple
T17147390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downhill Double Dipper |
E416124
|
entity |
| Predicate | hasQueueAccessibility |
P126294
|
FINISHED |
| Object | accessible via stairs |
—
|
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: accessible via stairs | Statement: [Downhill Double Dipper, hasQueueAccessibility, accessible via stairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueueAccessibility Context triple: [Downhill Double Dipper, hasQueueAccessibility, accessible via stairs]
-
A.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
B.
hasQueueRequirement
Indicates that an entity must satisfy or adhere to a specified queue-related condition or rule.
-
C.
hasQueueType
Indicates that an entity is associated with a specific type or category of queue.
-
D.
usesQueue
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
E.
hasAccessibilityFocus
Indicates that a user interface element is currently the primary target of accessibility tools, such as screen readers or keyboard navigation, receiving focused attention for interaction.
- F. None of above. chosen
Provenance (4 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f404f0e88190b7ac9ac523fdc7da |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.