Triple
T30347688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Jump Comics |
E771908
|
entity |
| Predicate | associatedWithMagazine |
P84334
|
FINISHED |
| Object | Weekly Young Jump |
E772882
|
NE FINISHED |
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, associatedWithMagazine, Weekly Young Jump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMagazine Context triple: [Young Jump Comics, associatedWithMagazine, Weekly Young Jump]
-
A.
relationshipToMagazine
chosen
Indicates the type of connection or association an entity has with a particular magazine, such as authorship, editorship, or other defined roles or links.
-
B.
ownedMagazine
Indicates that one entity possessed or held ownership of a particular magazine.
-
C.
associatedWithNewspaper
Indicates a relationship where an entity is connected or linked to a newspaper, such as through ownership, employment, contribution, or representation.
-
D.
appearsInMagazine
Indicates that an entity is featured, mentioned, or otherwise present within a particular magazine.
-
E.
modeledForMagazine
Indicates that an entity posed as a model specifically for a magazine publication.
- F. None of above.
Provenance (4 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277c28f12c8190a703fc2c9b2fe97a |
completed | June 9, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:56 p.m.