Triple
T30346900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Square |
E771890
|
entity |
| Predicate | serializedWork |
P161651
|
FINISHED |
| Object | Blue Exorcist |
—
|
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: Blue Exorcist | Statement: [Jump Square, serializedWork, Blue Exorcist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serializedWork Context triple: [Jump Square, serializedWork, Blue Exorcist]
-
A.
workSerializedIn
chosen
Indicates that a creative work is published or presented in serialized form within a larger publication or series (e.g., in a magazine, journal, or anthology).
-
B.
transmittedWork
Indicates that a work (such as information, data, or content) has been sent or conveyed from one entity to another.
-
C.
stagedWorkBy
Indicates that a particular staging or production of a work (such as a play, opera, or performance) was created, directed, or otherwise realized by a specific person or organization.
-
D.
issuedWork
Indicates that an entity has formally produced, published, or released a particular work.
-
E.
compilesWorkOf
Indicates that one entity gathers, edits, or assembles the works created by another entity into a collection or compilation.
- 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_69f682084db081909e261c5bbae024e3 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.