Triple
T29142254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valiant Comics |
E738668
|
entity |
| Predicate | hasSharedUniverse |
P41009
|
FINISHED |
| Object | Valiant Universe |
—
|
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: Valiant Universe | Statement: [Valiant Comics, hasSharedUniverse, Valiant Universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSharedUniverse Context triple: [Valiant Comics, hasSharedUniverse, Valiant Universe]
-
A.
sharesFictionalUniverseWith
Indicates that two entities are set within the same fictional universe or continuity, such that their stories coexist in a shared narrative world.
-
B.
hasMultiverseDesignation
Indicates that an entity is assigned a specific identifier or code distinguishing it within a multiverse or multiple-universe context.
-
C.
associatedUniverse
chosen
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
livesInWorldWith
Indicates that one entity exists or resides within the same world or universe as another entity.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 11:37 a.m.