Triple
T36605277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Barnstormer |
E903027
|
entity |
| Predicate | supportsVirtualQueue |
P132011
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [The Barnstormer, supportsVirtualQueue, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVirtualQueue Context triple: [The Barnstormer, supportsVirtualQueue, no]
-
A.
usesVirtualQueueSystem
chosen
Indicates that an entity manages access or service order through a virtual queuing mechanism rather than a traditional physical line.
-
B.
virtualQueueName
Indicates the name assigned to a specific virtual queue used to organize or route items, tasks, or participants.
-
C.
usesQueue
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
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.
supportsQualityOfService
Indicates that one entity provides or enables quality-of-service guarantees or capabilities for another entity or interaction.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.