Triple
T31192672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Dynamo |
E795222
|
entity |
| Predicate | firstCrimsonDynamoRealName |
P9233
|
FINISHED |
| Object | Anton Vanko |
E1087035
|
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: Anton Vanko | Statement: [Crimson Dynamo, firstCrimsonDynamoRealName, Anton Vanko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCrimsonDynamoRealName Context triple: [Crimson Dynamo, firstCrimsonDynamoRealName, Anton Vanko]
-
A.
championFullName
Indicates that the predicate specifies the complete, formal name of a champion.
-
B.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
C.
protagonistFullName
Indicates that the subject entity is the full, proper name (including given and family names) of the story’s main protagonist.
-
D.
titleCharacterRealName
Indicates that a character known by a title or alias has the specified real (personal) name.
-
E.
supervillainName
Indicates that an entity is known by a particular supervillain name or alias.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a296bd5e7ac8190852dcab9b8501109 |
completed | June 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:08 p.m.