Triple
T30346745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClariS |
E771886
|
entity |
| Predicate | performedOpeningTheme |
P21830
|
FINISHED |
| Object | Connect |
—
|
NE NERFINISHED |
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: Connect | Statement: [ClariS, performedOpeningTheme, Connect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedOpeningTheme Context triple: [ClariS, performedOpeningTheme, Connect]
-
A.
openingThemePerformer
chosen
Indicates the performer or group responsible for performing the opening theme of a work (such as a TV show, film, or game).
-
B.
openingThemeComposer
Indicates that the subject is the person who composed the musical opening theme for the specified work or production.
-
C.
performedThemeFor
Indicates that an agent carried out or executed a performance specifically for a particular theme or subject.
-
D.
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.
-
E.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 29, 2026, 7:56 p.m.