Triple

T21518951
Position Surface form Disambiguated ID Type / Status
Subject Ogi E530921 entity
Predicate mergedInto P77 FINISHED
Object Sado 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: Sado | Statement: [Ogi, mergedInto, Sado]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sado
Context triple: [Ogi, mergedInto, Sado]
  • A. Sado
    Sado is the eponymous figure associated with the Sadozai lineage, a notable tribal or dynastic group in the Pashtun/Afghan historical context.
  • B. Sado chosen
    Sado is a city on Sado Island in Niigata Prefecture, Japan, known for its rich history, traditional culture, and scenic coastal landscapes.
  • C. Queen Sado
    Queen Sado was a queen consort of the Korean kingdom of Silla, best known as the wife of King Jinheung and a key figure in the royal lineage of early Silla.
  • D. Futa Tooro
    Futa Tooro is a historic region along the Senegal River in West Africa, known as a heartland of Pulaar-speaking peoples and an important center of Islamic scholarship and resistance to colonial rule.
  • E. Shunga
    Shunga was an ancient Indian dynasty that succeeded the Maurya Empire and ruled much of northern and central India in the 2nd–1st centuries BCE.
  • 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_69e0c45d95a081908e7962ad215da746 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee884af0f08190bc1f3d70e57a325d completed April 26, 2026, 9:48 p.m.
Created at: April 16, 2026, 6:25 p.m.