Triple
T24431566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Effect mobile games |
E616012
|
entity |
| Predicate | gameplayAdaptationFor |
P156113
|
FINISHED |
| Object | handheld devices |
—
|
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: handheld devices | Statement: [Mass Effect mobile games, gameplayAdaptationFor, handheld devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayAdaptationFor Context triple: [Mass Effect mobile games, gameplayAdaptationFor, handheld devices]
-
A.
gameplayImpact
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
B.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
C.
gameplayBasis
Indicates that one entity serves as the core mechanic, structure, or inspiration upon which another entity’s gameplay is designed or derived.
-
D.
stageAdaptation
Indicates that one work has been adapted into a performance intended for the stage, such as a play or musical.
-
E.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29783b3208190997c47be1aa229af |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.