Triple

T13915887
Position Surface form Disambiguated ID Type / Status
Subject Yassa E334619 entity
Predicate alsoKnownAs P39 FINISHED
Object Yasa E334619 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: Yasa | Statement: [Yassa, alsoKnownAs, Yasa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yasa
Context triple: [Yassa, alsoKnownAs, Yasa]
  • A. Yassa chosen
    Yassa was the codified legal and administrative code traditionally attributed to Genghis Khan that governed the Mongol Empire and its successor states.
  • B. Yahi
    The Yahi were a small Native American group from northern California, known for being among the last surviving independent Indigenous peoples in the region and for the story of Ishi, their last known member.
  • C. Yawal
    Yawal is a town in the Indian state of Maharashtra, situated in the Jalgaon district and known for its agricultural surroundings and local markets.
  • D. Yoso
    Yoso was a short-lived progressive rock supergroup formed by former members of Yes and Toto, blending classic prog influences with melodic rock.
  • E. Yasa'ur
    Yasa'ur was a Mongol prince and military leader who played a significant role in the politics and conflicts of the Chagatai Khanate during the early 14th century.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de27260ae08190be45b4b15898e365 completed April 14, 2026, 11:38 a.m.
NED1 Entity disambiguation (via context triple) batch_69fba1c26ba08190b19560123691fda4 completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:16 p.m.