Triple
T33655833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky the Musical |
E862217
|
entity |
| Predicate | notableStagingFeature |
P61000
|
FINISHED |
| Object | onstage boxing ring |
—
|
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: onstage boxing ring | Statement: [Rocky the Musical, notableStagingFeature, onstage boxing ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStagingFeature Context triple: [Rocky the Musical, notableStagingFeature, onstage boxing ring]
-
A.
notableStage
Indicates that an entity is recognized as an important or distinguished stage or phase in relation to another entity or process.
-
B.
notableStyleFeature
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
-
C.
notableTechnicalFeature
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
-
D.
staging
Indicates the process of arranging, organizing, or setting up elements in preparation for a main event, performance, or deployment.
-
E.
notableFeatureOn
chosen
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:42 a.m.