Triple
T11907021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boneyard |
E283295
|
entity |
| Predicate | hasQueueRequirement |
P102279
|
FINISHED |
| Object | no ride vehicle |
—
|
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 vehicle | Statement: [The Boneyard, hasQueueRequirement, no ride vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueueRequirement Context triple: [The Boneyard, hasQueueRequirement, no ride vehicle]
-
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.
hasQueueType
Indicates that an entity is associated with a specific type or category of queue.
-
C.
usesQueue
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
D.
hasEntryRequirement
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
-
E.
hasWaitingList
Indicates that there exists a queue or list of entities waiting for access to, or participation in, the referenced resource, service, or opportunity.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5264b2081909bda6c24abb89725 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.