Triple
T29089455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Kombat II |
E734813
|
entity |
| Predicate | subBossCharacter |
P166298
|
FINISHED |
| Object | Kintaro |
—
|
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: Kintaro | Statement: [Mortal Kombat II, subBossCharacter, Kintaro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subBossCharacter Context triple: [Mortal Kombat II, subBossCharacter, Kintaro]
-
A.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
B.
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.
-
C.
fictionalBossOf
Indicates a relationship where one entity is the boss or superior of another within a fictional or imagined context.
-
D.
roleInHorribleBosses
Indicates that an entity has a specific acting role or character appearance in the movie "Horrible Bosses."
-
E.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
- F. None of above. chosen
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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:03 a.m.