Triple
T32686951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Ostrander |
E835750
|
entity |
| Predicate | notableCharacterDeveloped |
—
|
GENERATED |
| Object | Deadshot |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterDeveloped Context triple: [John Ostrander, notableCharacterDeveloped, Deadshot]
-
A.
developedCharacter
chosen
Indicates that one entity created, designed, or otherwise brought into existence the character represented by the other entity.
-
B.
notableCharacterCreated
Indicates that one entity is a notable or significant character that was created by another entity.
-
C.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
D.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
E.
notableSeriesCharacter
Indicates that an entity is a significant or well-known character appearing in a particular series.
- F. None of above.
Provenance (1 batch)
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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:09 a.m.