Triple

T6060891
Position Surface form Disambiguated ID Type / Status
Subject Late Middle Japanese E135028 entity
Predicate hasKeyChange P68407 FINISHED
Object simplification of certain Old Japanese morphological distinctions 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: simplification of certain Old Japanese morphological distinctions | Statement: [Late Middle Japanese, hasKeyChange, simplification of certain Old Japanese morphological distinctions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKeyChange
Context triple: [Late Middle Japanese, hasKeyChange, simplification of certain Old Japanese morphological distinctions]
  • A. hasKeyChanges
    Indicates that one entity undergoes or contains changes in musical key relative to another entity or version.
  • B. hasKeyAction
    Indicates that an entity performs or is associated with a primary or essential action within a given context.
  • C. hasKeyElement
    Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
  • D. hasKeyFunction
    Indicates that one entity serves as a primary or essential function or role for another entity.
  • E. hasKeyActivity
    Indicates that an entity is associated with or performs a primary or central activity.
  • F. None of above. chosen

Provenance (4 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_69c00878d06881909ee78e88913bf890 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0571fcecc8190a68e0d0668bbbfa7 completed March 22, 2026, 8:54 p.m.
PD Predicate disambiguation batch_69c049f031408190b08b2766237c5dd0 completed March 22, 2026, 7:58 p.m.
PDg Predicate description generation batch_69c04e8d4a148190bd8f95caae978e1b completed March 22, 2026, 8:18 p.m.
Created at: March 22, 2026, 4:10 p.m.