Triple
T19632848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal’s Volcano Bay |
E471313
|
entity |
| Predicate | queueSystemType |
P24240
|
FINISHED |
| Object | virtual 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: virtual queue | Statement: [Universal’s Volcano Bay, queueSystemType, virtual queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueSystemType Context triple: [Universal’s Volcano Bay, queueSystemType, virtual queue]
-
A.
queueType
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
B.
queueTypical
Indicates that an entity is in or follows a standard or commonly expected queueing order or behavior relative to others.
-
C.
hasQueueType
chosen
Indicates that an entity is associated with a specific type or category of queue.
-
D.
queueInterface
Indicates that one entity serves as a queue interface through which another entity can enqueue, dequeue, or otherwise manage queued items or requests.
-
E.
queueBehavior
Indicates how an entity manages or responds to items or events in a queue, such as their order, timing, or handling strategy.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6410449ec8190b8c20c0e09cd9156 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.