Triple

T29100863
Position Surface form Disambiguated ID Type / Status
Subject Shin Megami Tensei E736635 entity
Predicate notableMechanicInfluence P45664 FINISHED
Object influenced demon-collecting RPGs 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: influenced demon-collecting RPGs | Statement: [Shin Megami Tensei, notableMechanicInfluence, influenced demon-collecting RPGs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableMechanicInfluence
Context triple: [Shin Megami Tensei, notableMechanicInfluence, influenced demon-collecting RPGs]
  • A. notableMechanicOrigin
    Indicates that a mechanic is notably associated with or originates from a particular source, such as a creator, work, or context.
  • B. notableLevelMechanic
    Indicates that an entity is recognized for its significant involvement in designing, implementing, or innovating game level mechanics.
  • C. hadInfluenceOn chosen
    Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
  • D. wereInfluencedBy
    Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
  • E. notableImpactOn
    Indicates that one entity has had a significant, recognizable, or influential effect on another entity.
  • 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_69f077ec765c81909474c88bcc8bab43 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_6a02f10505988190be5fd57566a90e0f completed May 12, 2026, 9:21 a.m.
PD Predicate disambiguation batch_6a02f03a8c1481909e137e270119f7ef completed May 12, 2026, 9:17 a.m.
Created at: April 28, 2026, 11:12 a.m.