Triple
T28896797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed Boon |
E732853
|
entity |
| Predicate | basedOnPseudonym |
P3799
|
FINISHED |
| Object | Noob Saibot (Mortal Kombat character) |
—
|
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: Noob Saibot (Mortal Kombat character) | Statement: [Ed Boon, basedOnPseudonym, Noob Saibot (Mortal Kombat character)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPseudonym Context triple: [Ed Boon, basedOnPseudonym, Noob Saibot (Mortal Kombat character)]
-
A.
basedOnAuthorPseudonym
Indicates that something is derived from, inspired by, or determined using an author's pseudonym rather than their real name.
-
B.
usedPseudonym
chosen
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
C.
usedPseudonymWith
Indicates that one entity employed a pseudonym or alias when interacting or being associated with another entity.
-
D.
basedOnAuthorRealName
Indicates that one entity is derived from, inspired by, or uses the real (legal) name of an author as its basis.
-
E.
pseudonymPurpose
Indicates that a pseudonym is used for a specific purpose, function, or intended use in a given context.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 7:59 a.m.