Triple
T29273091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Kombat: Armageddon |
E742171
|
entity |
| Predicate | numberOfPlayableCharactersApprox |
P48193
|
FINISHED |
| Object | over 60 |
—
|
LITERAL 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: over 60 | Statement: [Mortal Kombat: Armageddon, numberOfPlayableCharactersApprox, over 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPlayableCharactersApprox Context triple: [Mortal Kombat: Armageddon, numberOfPlayableCharactersApprox, over 60]
-
A.
numberOfPlayableCharacters
chosen
Indicates the total count of distinct characters that can be actively controlled or played by a user in a game or interactive experience.
-
B.
numberOfCharacters
Indicates the total count of individual characters present in a given text, string, or entity’s representation.
-
C.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
D.
numberOfHumanCharacters
Indicates the count of distinct human characters associated with a given entity or context.
-
E.
numberOfHumanProtagonists
Indicates the count of human characters that serve as protagonists in a given work or 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: April 28, 2026, 12:49 p.m.