Triple
T12574350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Apocalypse War |
E300166
|
entity |
| Predicate | firstAppearedInIssueRange |
P78612
|
FINISHED |
| Object | 2000 AD progs 245–270 |
—
|
LITERAL 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: 2000 AD progs 245–270 | Statement: [The Apocalypse War, firstAppearedInIssueRange, 2000 AD progs 245–270]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearedInIssueRange Context triple: [The Apocalypse War, firstAppearedInIssueRange, 2000 AD progs 245–270]
-
A.
currentSeriesIssueStart
Indicates that something marks the starting point or first issue of the current series.
-
B.
firstAppearanceInComicsIssue
chosen
Indicates the specific comic book issue in which an entity (such as a character or item) is depicted for the first time.
-
C.
firstIssueCoverDate
Indicates the date on which the first issue of something (such as a series, publication, or comic) was initially released or covered.
-
D.
firstAppearancePublisher
Indicates the publisher responsible for releasing an entity’s first appearance.
-
E.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 4:44 p.m.