Triple

T8550148
Position Surface form Disambiguated ID Type / Status
Subject Kundalakesi E202424 entity
Predicate textualCondition P83269 FINISHED
Object reconstructed from secondary sources 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: reconstructed from secondary sources | Statement: [Kundalakesi, textualCondition, reconstructed from secondary sources]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: textualCondition
Context triple: [Kundalakesi, textualCondition, reconstructed from secondary sources]
  • A. variableCondition
    Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
  • B. containsText
    Indicates that one entity includes the specified text string within its content.
  • C. coreCondition
    Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
  • D. textualFunction
    Indicates a functional or structural role that a text segment serves within a larger document or discourse (e.g., title, caption, summary, instruction).
  • E. languageCriterion
    Indicates that a relationship or selection is based on whether something meets a specified language-related requirement or condition.
  • 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_69ca832610e08190b3b6c6cd2c250255 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe75589d8819096177ddbd3dafcb6 completed March 31, 2026, 3:25 p.m.
PD Predicate disambiguation batch_69cbd113e05c81908f4f3fc1b5925164 completed March 31, 2026, 1:50 p.m.
PDg Predicate description generation batch_69cbe30d453481908f897ed2b06e7534 completed March 31, 2026, 3:06 p.m.
Created at: March 30, 2026, 6:19 p.m.