Triple
T29097692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abomination |
E735053
|
entity |
| Predicate | mcuRealName |
P9233
|
FINISHED |
| Object | Emil Blonsky |
—
|
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: Emil Blonsky | Statement: [Abomination, mcuRealName, Emil Blonsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mcuRealName Context triple: [Abomination, mcuRealName, Emil Blonsky]
-
A.
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.
-
B.
notRealNameOf
Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that entity).
-
C.
nameOf
Indicates that one entity is the name or designation of another entity.
-
D.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
E.
transcribedName
Indicates that one entity is a written or phonetic rendering of another entity’s name, typically adapted to a different script, language, or transcription system.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66182260081908996c0c2fd6d4f0e |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:10 a.m.