Triple
T17888223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DC Rebirth |
E447247
|
entity |
| Predicate | restoresElement |
P129168
|
FINISHED |
| Object | legacy of classic DC characters |
—
|
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: legacy of classic DC characters | Statement: [DC Rebirth, restoresElement, legacy of classic DC characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoresElement Context triple: [DC Rebirth, restoresElement, legacy of classic DC characters]
-
A.
restoredSymbol
Indicates that an entity has been brought back or reinstated as a symbol after having been altered, removed, or lost.
-
B.
restoredFeature
Indicates that an entity has brought a previously removed, damaged, or inactive feature back to its original or intended functional state.
-
C.
restoredRight
Indicates that a previously lost, removed, or suspended right has been returned to its holder.
-
D.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
E.
restoringMechanism
Indicates a mechanism or process that returns something to its original, proper, or functional state after change, damage, or deviation.
- F. None of above. chosen
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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c15f8b08190ac8d134e32d62d18 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:18 a.m.