Triple
T864600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitty-Chitty-Bang-Bang |
E18672
|
entity |
| Predicate | musicalFormat |
P130
|
FINISHED |
| Object | stage musical |
—
|
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: stage musical | Statement: [Chitty-Chitty-Bang-Bang, musicalFormat, stage musical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalFormat Context triple: [Chitty-Chitty-Bang-Bang, musicalFormat, stage musical]
-
A.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
B.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
C.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
musicFusionOf
Indicates a relationship where one musical work, style, or element is created by combining or blending two or more distinct musical sources or genres.
-
E.
musicBrainzType
Indicates the specific MusicBrainz-defined category or classification assigned to an entity within the MusicBrainz database.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac6acc148190bcc00a1e939ace77 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.