Triple
T30346746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClariS |
E771886
|
entity |
| Predicate | performedOpeningFor |
P104136
|
FINISHED |
| Object | Puella Magi Madoka Magica |
—
|
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: Puella Magi Madoka Magica | Statement: [ClariS, performedOpeningFor, Puella Magi Madoka Magica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedOpeningFor Context triple: [ClariS, performedOpeningFor, Puella Magi Madoka Magica]
-
A.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
B.
hasOpenedFor
chosen
Indicates that one entity has performed or appeared as the opening act or preliminary participant for another entity, typically in an event or performance context.
-
C.
operatorAtOpening
Indicates that an operator is present and on duty at the time of an opening event.
-
D.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
E.
performedUnder
Indicates that an action or task was carried out subject to, or within the scope of, a particular condition, authority, context, or framework.
- 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_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 29, 2026, 7:56 p.m.