Triple
T977860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshi’s Adventure |
E21096
|
entity |
| Predicate | hasQueueArea |
P3382
|
FINISHED |
| Object | indoor queue |
—
|
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: indoor queue | Statement: [Yoshi’s Adventure, hasQueueArea, indoor queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQueueArea Context triple: [Yoshi’s Adventure, hasQueueArea, indoor queue]
-
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.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
hasStopArea
Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
-
D.
hasSpectatorArea
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
E.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47861808190be56a7bbd926e658 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a8a3b08190b4538e119b13f7f5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:40 p.m.