Triple
T24754620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Effect Legendary Edition |
E619245
|
entity |
| Predicate | includesMultiplayer |
P43216
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Mass Effect Legendary Edition, includesMultiplayer, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMultiplayer Context triple: [Mass Effect Legendary Edition, includesMultiplayer, false]
-
A.
hasMultiplayer
chosen
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
B.
multiplayerFeature
Indicates that the subject supports or involves multiple users participating together, typically at the same time within the same activity or environment.
-
C.
supportsOnlineMultiplayer
Indicates that the subject provides functionality for multiple users to play together over an online network.
-
D.
supportsLocalMultiplayer
Indicates that the subject provides functionality for multiple players to play together on the same device or local network.
-
E.
multiplayerType
Indicates the type or mode of multiplayer interaction supported between participants.
- 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_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 4:25 a.m.