Triple

T19595170
Position Surface form Disambiguated ID Type / Status
Subject Hindu mythology E470331 entity
Predicate featuresDeity P20396 FINISHED
Object Surya 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: Surya | Statement: [Hindu mythology, featuresDeity, Surya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Surya
Context triple: [Hindu mythology, featuresDeity, Surya]
  • A. Surya chosen
    Surya is the Hindu sun god revered as a major solar deity associated with light, power, and vitality.
  • B. Сунжа
    Сунжа — это река на Северном Кавказе, протекающая через Чечню и Ингушетию и играющая важную роль в водной системе региона.
  • C. Sunena
    Sunena is an Indian feminine given name, typically considered a variant of the name Sunaina.
  • D. Solnice
    Solnice is a small town in the Hradec Králové Region of the Czech Republic, known for its industrial facilities and proximity to the Orlické Mountains.
  • E. Inti
    Inti is the Incan sun god, revered as a principal deity associated with royal power, agriculture, and the cosmic order.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640793cd88190b9b84491bfb2493f completed April 20, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:43 p.m.