Triple
T24754589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Effect Legendary Edition |
E619245
|
entity |
| Predicate | includesDownloadableContent |
P39175
|
FINISHED |
| Object | Mass Effect DLC packs |
—
|
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: Mass Effect DLC packs | Statement: [Mass Effect Legendary Edition, includesDownloadableContent, Mass Effect DLC packs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDownloadableContent Context triple: [Mass Effect Legendary Edition, includesDownloadableContent, Mass Effect DLC packs]
-
A.
supportsDigitalDownloads
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
B.
distributionIncludes
Indicates that a distribution or release of something contains or encompasses the specified item or component.
-
C.
hasDLC
chosen
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
D.
dataIncluded
Indicates that one data item or dataset contains, incorporates, or subsumes another as part of its contents.
-
E.
catalogueIncludes
Indicates that a catalogue contains or lists a particular item as part of its contents.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 4:25 a.m.