Triple
T33828510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh Jean |
E867026
|
entity |
| Predicate | includedInMusical |
P21695
|
FINISHED |
| Object | Sunshine on Leith (stage musical) |
E247358
|
NE 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: Sunshine on Leith (stage musical) | Statement: [Oh Jean, includedInMusical, Sunshine on Leith (stage musical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInMusical Context triple: [Oh Jean, includedInMusical, Sunshine on Leith (stage musical)]
-
A.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
partOfMusical
chosen
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
C.
isMusicalWork
Indicates that one entity is a musical composition or piece created as an artistic work.
-
D.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
E.
usesMusicalElement
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
- F. None of above.
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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36760f274c8190ab54ea2df71fcb8b |
completed | June 20, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:46 a.m.