Triple
T29796223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Kombat: Legacy |
E756556
|
entity |
| Predicate | webChannel |
P61714
|
FINISHED |
| Object | Machinima.com |
—
|
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: Machinima.com | Statement: [Mortal Kombat: Legacy, webChannel, Machinima.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webChannel Context triple: [Mortal Kombat: Legacy, webChannel, Machinima.com]
-
A.
virtualChannel
Indicates that one entity is linked to another through a non-physical, software-defined communication channel used for transmitting data or signals.
-
B.
ownedChannel
chosen
Indicates that one entity possesses ownership or control over a particular channel.
-
C.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
D.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
E.
webUse
Indicates that an entity uses or interacts with another entity via the web or through web-based functionality.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e690f081908e0992c9ae27c71e |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:15 p.m.