Triple
T20155750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raptor Encounter |
E491560
|
entity |
| Predicate | queueStyle |
P138875
|
FINISHED |
| Object | periodic set showtimes |
—
|
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: periodic set showtimes | Statement: [Raptor Encounter, queueStyle, periodic set showtimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueStyle Context triple: [Raptor Encounter, queueStyle, periodic set showtimes]
-
A.
queueType
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
B.
queueBehavior
Indicates how an entity manages or responds to items or events in a queue, such as their order, timing, or handling strategy.
-
C.
queueTypical
Indicates that an entity is in or follows a standard or commonly expected queueing order or behavior relative to others.
-
D.
queueAreaTheme
Indicates the thematic style or concept applied to the area where people wait in line for an attraction or service.
-
E.
queueInterface
Indicates that one entity serves as a queue interface through which another entity can enqueue, dequeue, or otherwise manage queued items or requests.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667df7ac081908816d2d29e7c6513 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:34 p.m.