Triple

T26557944
Position Surface form Disambiguated ID Type / Status
Subject Vikramaditya E666161 entity
Predicate historicCoreLinkedTo P16345 FINISHED
Object Chandragupta II Vikramaditya 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: Chandragupta II Vikramaditya | Statement: [Vikramaditya, historicCoreLinkedTo, Chandragupta II Vikramaditya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicCoreLinkedTo
Context triple: [Vikramaditya, historicCoreLinkedTo, Chandragupta II Vikramaditya]
  • A. historicCore
    Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
  • B. historicallyLinked chosen
    Indicates that two entities are connected through a shared or related historical event, period, or development.
  • C. historicalCoreOf
    Indicates that one entity constitutes the original or most historically significant central part of another entity.
  • D. historicSeeOf
    Indicates that a place serves or has served as the principal episcopal seat or central ecclesiastical jurisdiction of a bishop or similar religious authority.
  • E. historicFor
    Indicates that something holds historical significance or importance specifically in relation to 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_69ee9cf7e94481909f0d556b36e43572 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69fba2877b248190a974eb092243c0c4 completed May 6, 2026, 8:20 p.m.
PD Predicate disambiguation batch_69fb8d06a1b48190a937aa410d159dfa completed May 6, 2026, 6:48 p.m.
Created at: April 27, 2026, 1:51 a.m.