Triple

T6771265
Position Surface form Disambiguated ID Type / Status
Subject Anyin language E155046 entity
Predicate hasAlternativeName P39 FINISHED
Object Agni E102074 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: Agni | Statement: [Anyin language, hasAlternativeName, Agni]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Agni
Context triple: [Anyin language, hasAlternativeName, Agni]
  • A. Agni chosen
    Agni is the Vedic god of fire, revered as a central deity of sacrifice and a divine messenger between humans and the gods in ancient Indian religion.
  • B. Anyin Agni
    Anyin Agni is a dialect of the Anyin language spoken by Agni communities, primarily in parts of Côte d’Ivoire and neighboring regions.
  • C. Rudra
    Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
  • D. Indra
    Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
  • E. Vivasvan
    Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
  • 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_69c68812ef7c819099369f51febb725c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d2496fa08190895d8b625fb0d699 completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a7da01c8190995885eeb4ba6253 completed March 28, 2026, 12:02 a.m.
Created at: March 27, 2026, 2:13 p.m.