Triple
T32555460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Others |
E832084
|
entity |
| Predicate | laterContinuity |
P162083
|
FINISHED |
| Object | DC Rebirth |
E447247
|
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: DC Rebirth | Statement: [The Others, laterContinuity, DC Rebirth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterContinuity Context triple: [The Others, laterContinuity, DC Rebirth]
-
A.
cultContinuity
Indicates the continuation or persistence of a religious cult’s practices, beliefs, or traditions over time.
-
B.
laterIdentityContinuityWith
Indicates that an entity at a later time is considered the same continuing individual or identity as an entity at an earlier time.
-
C.
titleContinuity
Indicates that two works share a continuous or consistent use of the same title across versions, installments, or related contexts.
-
D.
seriesContinuity
chosen
Indicates that one work, episode, or installment maintains narrative or canonical continuity with another within the same series.
-
E.
starContinuity
Indicates that there is an unbroken, consistent connection or progression involving a star (or stars) across time, space, or related contexts.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b8e1dd48190af10788b16b5cab7 |
completed | June 18, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 1, 2026, 1:03 a.m.