Triple

T16773915
Position Surface form Disambiguated ID Type / Status
Subject Spenta Mainyu E407673 entity
Predicate associatedWith P37 FINISHED
Object Asha E775065 NE 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: Asha | Statement: [Spenta Mainyu, associatedWith, Asha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asha
Context triple: [Spenta Mainyu, associatedWith, Asha]
  • A. Asha
    Asha is the given name of legendary Indian playback singer Asha Bhosle, renowned for her versatile and prolific contributions to Hindi cinema music.
  • B. Asha
    Asha is a line of budget-friendly Nokia mobile phones designed to offer smartphone-like features to emerging markets.
  • C. Asha chosen
    Asha is a central Zoroastrian and Iranian mythological concept representing truth, cosmic order, and righteousness that upholds the moral and natural structure of the universe.
  • D. Ascha
    Ascha is a small municipality in the district of Straubing-Bogen in Lower Bavaria, Germany.
  • E. Aruna
    Aruna is a figure in Hindu mythology known as the personified dawn and the divine charioteer who drives the sun god Surya across the sky.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8839270588190886720d9519bbf8f completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b038d0608190be15c758427bb664 completed April 18, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00aafc28c0819084ecd6e5be6adec9 completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:22 a.m.