Triple

T30943217
Position Surface form Disambiguated ID Type / Status
Subject Mountain Knot City E788316 entity
Predicate importanceInGameplay P118563 FINISHED
Object key progression point in main story 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: key progression point in main story | Statement: [Mountain Knot City, importanceInGameplay, key progression point in main story]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: importanceInGameplay
Context triple: [Mountain Knot City, importanceInGameplay, key progression point in main story]
  • A. gameplayImpact chosen
    Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
  • B. gameModeRelevance
    Indicates how strongly or in what way something is related or applicable to a particular game mode.
  • C. importanceInRacing
    Indicates the degree to which something plays a significant or influential role within the context of racing.
  • D. importanceInSeason
    Indicates the degree to which something is significant or influential within a specific season or seasonal context.
  • E. notableGameFeature
    Indicates that a particular game feature is especially significant, distinctive, or noteworthy in the context of the game.
  • 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_69f224c180f88190ad177372ee02b7e2 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6d6a6b04c8190bee4cf9c00665ef7 completed May 3, 2026, 5:01 a.m.
PD Predicate disambiguation batch_69f6d26ceb08819091c71c001e954936 completed May 3, 2026, 4:43 a.m.
Created at: April 29, 2026, 8:53 p.m.