Triple

T24874602
Position Surface form Disambiguated ID Type / Status
Subject Mass Effect: Galaxy E622532 entity
Predicate tiesInto P133150 FINISHED
Object Mass Effect 2 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 2 | Statement: [Mass Effect: Galaxy, tiesInto, Mass Effect 2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tiesInto
Context triple: [Mass Effect: Galaxy, tiesInto, Mass Effect 2]
  • A. tieInWith chosen
    Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
  • B. ties
    Indicates that one entity fastens, secures, or binds another entity (or two entities together), typically using a flexible connector such as a string, rope, or similar medium.
  • C. enteredIntoBy
    Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
  • D. tierRelation
    Indicates a hierarchical relationship where one entity is positioned at a specific level or rank relative to another within an ordered tier structure.
  • E. entangledWith
    Indicates a mutual state in which two or more entities are so interconnected that a change or condition in one inherently affects or constrains the other(s).
  • 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.