Triple
T30346747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClariS |
E771886
|
entity |
| Predicate | performedEndingFor |
P42947
|
FINISHED |
| Object | Nisemonogatari |
—
|
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: Nisemonogatari | Statement: [ClariS, performedEndingFor, Nisemonogatari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedEndingFor Context triple: [ClariS, performedEndingFor, Nisemonogatari]
-
A.
performedTo
chosen
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
B.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
C.
performedFrom
Indicates that an action or operation is carried out starting at or originating from a specified source location, context, or entity.
-
D.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
E.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
- 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_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 29, 2026, 7:56 p.m.