Triple
T29023133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Kombat 3 |
E737508
|
entity |
| Predicate | hasFinishingMoveType |
P80697
|
FINISHED |
| Object | Fatality |
—
|
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: Fatality | Statement: [Mortal Kombat 3, hasFinishingMoveType, Fatality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishingMoveType Context triple: [Mortal Kombat 3, hasFinishingMoveType, Fatality]
-
A.
hasFinishingMove
chosen
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
-
B.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
C.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
D.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
E.
canBeFinishedAs
Indicates that one entity (such as a task, process, or activity) is capable of being completed or brought to an end in the form or manner specified by another entity.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 28, 2026, 9:50 a.m.