Triple
T30482223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naoshi Komi |
E775615
|
entity |
| Predicate | serialisedIn |
P62614
|
FINISHED |
| Object | Weekly Shōnen 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 Shōnen Jump | Statement: [Naoshi Komi, serialisedIn, Weekly Shōnen Jump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serialisedIn Context triple: [Naoshi Komi, serialisedIn, Weekly Shōnen Jump]
-
A.
serializedIn
chosen
Indicates that something is published or presented in sequential installments within a larger medium or series.
-
B.
firstSerialisedIn
Indicates the original publication or medium in which something (such as a work or story) was first released in serialized form.
-
C.
serialized
Indicates that one entity has been converted into a sequential, storable or transmittable data format representing its structure or state.
-
D.
originallySerialized
Indicates that one entity was first stored, recorded, or encoded in a serialized form by another entity or process.
-
E.
isSerializableIn
Indicates that something can be converted into a specific format or representation suitable for storage or transmission within a given context or system.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:12 p.m.