Triple
T38069394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annihilation |
E950553
|
entity |
| Predicate | hasComponentSeries |
P196902
|
FINISHED |
| Object | Annihilation: Prologue |
E950553
|
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: Annihilation: Prologue | Statement: [Annihilation, hasComponentSeries, Annihilation: Prologue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentSeries Context triple: [Annihilation, hasComponentSeries, Annihilation: Prologue]
-
A.
hasSeriesElement
chosen
Indicates that something is a member or component within an ordered series associated with another entity.
-
B.
hasSubSeries
Indicates that one series is a subordinate or component series within a larger parent series.
-
C.
hasSupportSeries
Indicates that one entity is backed, reinforced, or maintained by a sequence or set of supporting elements provided by another entity.
-
D.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
E.
hasParentSeries
Indicates that a work or item belongs to, or is derived from, a broader parent series.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41711583d48190abb48a582b187fc5 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.