Triple
T28202917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Hero |
E716934
|
entity |
| Predicate | openingThemeType |
P169954
|
FINISHED |
| Object | instrumental |
—
|
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: instrumental | Statement: [My Hero, openingThemeType, instrumental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingThemeType Context triple: [My Hero, openingThemeType, instrumental]
-
A.
openingTheme
Indicates that one entity serves as the opening theme (such as a song or musical piece) for another entity, typically a show, series, or similar work.
-
B.
openingThemeBasedOn
Indicates that the opening theme of a work is derived from, inspired by, or adapted from another specified source.
-
C.
openingThemeComposer
Indicates that the subject is the person who composed the musical opening theme for the specified work or production.
-
D.
openingThemeCount
Indicates the number of distinct opening themes associated with an entity (such as a series, season, or show).
-
E.
openingConcept
Indicates that one concept serves as the initial or introductory element in relation to another concept, such as the first idea, section, or phase in a sequence or structure.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 10:33 p.m.