Triple
T24874680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Effect (2007 video game) |
E622533
|
entity |
| Predicate | remasteredIn |
P71635
|
FINISHED |
| Object | Mass Effect: Legendary Edition |
—
|
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: Mass Effect: Legendary Edition | Statement: [Mass Effect (2007 video game), remasteredIn, Mass Effect: Legendary Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remasteredIn Context triple: [Mass Effect (2007 video game), remasteredIn, Mass Effect: Legendary Edition]
-
A.
remasteredVersion
Indicates that one entity is a newly produced, higher-quality audio or visual version of another original recording or release.
-
B.
remadeFor
Indicates that one work has been recreated or adapted specifically for another context, audience, or medium.
-
C.
hasRemastering
chosen
Indicates that one version of a work is a remastered form derived from another version of the same work.
-
D.
hasRemasteredAppearanceIn
Indicates that an entity appears in a remastered version of a work or medium.
-
E.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:23 a.m.