Triple

T8559673
Position Surface form Disambiguated ID Type / Status
Subject Yamuna E202658 entity
Predicate sibling P363 FINISHED
Object Revanta E448872 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: Revanta | Statement: [Yamuna, sibling, Revanta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Revanta
Context triple: [Yamuna, sibling, Revanta]
  • A. Revanta chosen
    Revanta is a minor Hindu deity associated with horses, hunting, and protection of travelers, traditionally regarded as a son of the sun god Surya.
  • B. Renaelva
    Renaelva is a river in eastern Norway that flows through Hedmark county before joining the larger Glomma river.
  • C. Relva
    Relva is a civil parish located within the municipality of Ponta Delgada on São Miguel Island in the Azores, Portugal.
  • D. Valaquenta
    Valaquenta is a section of J.R.R. Tolkien’s legendarium that provides a mythological account of the Valar, the Maiar, and the cosmology of Middle-earth.
  • E. Ochtum
    The Ochtum is a river in northwestern Germany that flows through Lower Saxony and Bremen before joining the Weser.
  • 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_69ca8326e6c881908ff720d6abaebdc5 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe949974c8190a75d9c767ca5fa5a completed March 31, 2026, 3:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce894d82588190b558d5b2dc65eafe completed April 2, 2026, 3:20 p.m.
Created at: March 30, 2026, 6:20 p.m.