Triple
T18527518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohyah Drop Slide |
E452755
|
entity |
| Predicate | usesVirtualQueueSystem |
P132011
|
FINISHED |
| Object | TapuTapu wearable |
—
|
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: TapuTapu wearable | Statement: [Ohyah Drop Slide, usesVirtualQueueSystem, TapuTapu wearable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVirtualQueueSystem Context triple: [Ohyah Drop Slide, usesVirtualQueueSystem, TapuTapu wearable]
-
A.
usesQueue
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
B.
virtualQueueName
Indicates the name assigned to a specific virtual queue used to organize or route items, tasks, or participants.
-
C.
usedVirtualVoting
Indicates that an entity participated in a voting process through virtual or remote means rather than in person.
-
D.
requiresVirtualMachine
Indicates that one entity depends on or must be run within a virtual machine provided by another entity in order to function or be valid.
-
E.
hasVirtualExperience
Indicates that one entity possesses or has participated in a virtual or digitally simulated experience related to another entity.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533f9bd1081909743b24e290b7dfe |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.