Triple
T32702973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What’s Inside |
E836191
|
entity |
| Predicate | orderInShow |
P178631
|
FINISHED |
| Object | first musical number in Waitress |
—
|
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: first musical number in Waitress | Statement: [What’s Inside, orderInShow, first musical number in Waitress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInShow Context triple: [What’s Inside, orderInShow, first musical number in Waitress]
-
A.
displayOrder
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
B.
orderDisplayed
Indicates that a particular order is currently being shown or presented in a user interface or display context.
-
C.
airingOrder
Indicates the sequence in which items (such as episodes or installments) are broadcast or released to the public.
-
D.
orderInPlot
chosen
Indicates the sequential position or ordering of an event or element within the structure of a plot.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:10 a.m.