Triple
T28638408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Justice |
E724852
|
entity |
| Predicate | rebootedInImprint |
P117801
|
FINISHED |
| Object | Wonder Comics |
—
|
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: Wonder Comics | Statement: [Young Justice, rebootedInImprint, Wonder Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebootedInImprint Context triple: [Young Justice, rebootedInImprint, Wonder Comics]
-
A.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
B.
reissueImprint
chosen
Indicates that one entity is an imprint used specifically for a reissued version of another entity.
-
C.
hadImprint
Indicates that one entity bears or once bore a physical or symbolic mark, stamp, or impression produced by another entity.
-
D.
rebootAnnounced
Indicates that an official announcement has been made that a system, service, or process will be rebooted.
-
E.
rebootedOnNetwork
Indicates that a device or system was rebooted while connected to, or as part of operations on, a specific network.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a84f848190b5898ee7566fb84e |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:42 a.m.