Triple
T29868761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goro |
E758527
|
entity |
| Predicate | subBossIn |
P166298
|
FINISHED |
| Object | Mortal Kombat (1992 video game) |
—
|
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: Mortal Kombat (1992 video game) | Statement: [Goro, subBossIn, Mortal Kombat (1992 video game)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subBossIn Context triple: [Goro, subBossIn, Mortal Kombat (1992 video game)]
-
A.
subBossCharacter
chosen
Indicates that one character serves as a subordinate or secondary boss in relation to another character within a hierarchy.
-
B.
underboss
Indicates that one entity holds a subordinate but high-ranking leadership role directly beneath another, often acting as their primary deputy or second-in-command.
-
C.
subLeader
Indicates that one entity serves as a subordinate or deputy leader under the authority of another leader entity.
-
D.
stageBossOf
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
E.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6768b2bf48190af4821d43d7ee766 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:52 p.m.