Triple

T16528821
Position Surface form Disambiguated ID Type / Status
Subject Kondhana E401507 entity
Predicate renamedByTradition P50138 FINISHED
Object after Tanaji’s death, symbolizing ‘Lion’s Fort’ 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: after Tanaji’s death, symbolizing ‘Lion’s Fort’ | Statement: [Kondhana, renamedByTradition, after Tanaji’s death, symbolizing ‘Lion’s Fort’]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: renamedByTradition
Context triple: [Kondhana, renamedByTradition, after Tanaji’s death, symbolizing ‘Lion’s Fort’]
  • A. replacedTraditionalName
    Indicates that one name has taken the place of, or superseded, an earlier traditional name for the same entity.
  • B. hasTraditionalName
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • C. changedNameInHonorOf chosen
    Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
  • D. belongsToNamingTradition
    Indicates that an entity is associated with or classified under a particular naming tradition or convention.
  • E. renamedInCentury
    Indicates that an entity underwent a renaming during the specified century.
  • 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_69d883838abc8190bc79cb2d41733ce2 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32ed57be481908625d4c5aab0940c completed April 18, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69e296995d388190b88ebe189dce890d completed April 17, 2026, 8:22 p.m.
Created at: April 10, 2026, 5:14 a.m.