Triple
T32973883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goofy’s Sky School area |
E843599
|
entity |
| Predicate | hasQueueAreaFor |
P3382
|
FINISHED |
| Object | Goofy’s Sky School |
—
|
NE NERFINISHED |
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: Goofy’s Sky School | Statement: [Goofy’s Sky School area, hasQueueAreaFor, Goofy’s Sky School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueueAreaFor Context triple: [Goofy’s Sky School area, hasQueueAreaFor, Goofy’s Sky School]
-
A.
hasWaitingArea
chosen
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
B.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
C.
queueAreaFeature
Indicates that a feature or characteristic is associated with, or forms part of, a queue area.
-
D.
hasQueueAccessibility
Indicates that an entity provides accessible features or accommodations for people with disabilities in its queuing or waiting areas.
-
E.
hasQueueRequirement
Indicates that an entity must satisfy or adhere to a specified queue-related condition or rule.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:22 a.m.