Triple
T32779033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journey into Mystery |
E838298
|
entity |
| Predicate | titleChangeIssue |
P176228
|
FINISHED |
| Object | Journey into Mystery #126 |
—
|
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: Journey into Mystery #126 | Statement: [Journey into Mystery, titleChangeIssue, Journey into Mystery #126]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleChangeIssue Context triple: [Journey into Mystery, titleChangeIssue, Journey into Mystery #126]
-
A.
titleChangedBy
Indicates that an entity’s title has been modified as a result of an action performed by another specified entity.
-
B.
isTitleChange
chosen
Indicates that an entity’s title has been modified from a previous title to a new one.
-
C.
issuesTitle
Indicates that an entity formally grants or assigns an official title or designation to another entity.
-
D.
titleChangeMethod
Indicates the method or process by which a title is changed from one state or holder to another.
-
E.
titleBecomes
Indicates that one title changes into or is replaced by another title over time.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 1, 2026, 1:13 a.m.