Triple
T30347689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Jump Comics |
E771908
|
entity |
| Predicate | publishesSeriesFrom |
P92830
|
FINISHED |
| Object | Weekly Young Jump |
—
|
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: Weekly Young Jump | Statement: [Young Jump Comics, publishesSeriesFrom, Weekly Young Jump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesSeriesFrom Context triple: [Young Jump Comics, publishesSeriesFrom, Weekly Young Jump]
-
A.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
B.
hasPublicationSeries
Indicates that an entity is part of, or associated with, a particular publication series.
-
C.
publisherOfSeries
chosen
Indicates that an entity serves as the publishing organization responsible for producing or distributing a particular series.
-
D.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
E.
releaseSeries
Indicates that one entity publishes or makes available a sequence of related releases (such as episodes, issues, or installments) as part of an ongoing series.
- 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_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 29, 2026, 7:56 p.m.