Triple
T27810243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of the Storm: Captain Jack’s Stunt Spectacular |
E702497
|
entity |
| Predicate | hasShowFormat |
P170980
|
FINISHED |
| Object | scripted performance |
—
|
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: scripted performance | Statement: [Eye of the Storm: Captain Jack’s Stunt Spectacular, hasShowFormat, scripted performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShowFormat Context triple: [Eye of the Storm: Captain Jack’s Stunt Spectacular, hasShowFormat, scripted performance]
-
A.
basedOnShowFormat
Indicates that one entity’s structure, style, or format is derived from or modeled after the format of a particular show.
-
B.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
C.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
-
D.
showFormatRole
Indicates the role or function that an entity has in relation to the format of a show or presentation.
-
E.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 5:42 p.m.