Triple

T20613994
Position Surface form Disambiguated ID Type / Status
Subject Orot and Kelim E506518 entity
Predicate operatesWithin P794 FINISHED
Object Asiyah 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: Asiyah | Statement: [Orot and Kelim, operatesWithin, Asiyah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asiyah
Context triple: [Orot and Kelim, operatesWithin, Asiyah]
  • A. Assiyah chosen
    Assiyah is the lowest of the four Kabbalistic worlds, representing the realm of physical creation and action.
  • B. Asinia
    Asinia was a Roman voting tribe (tribus) that formed part of the administrative and electoral organization of the Roman citizen body.
  • C. Asi
    Asi is an Austronesian language spoken primarily on Tablas Island in the Philippines.
  • D. Mawarannahr
    Mawarannahr is the historical region of Transoxiana in Central Asia, centered between the Amu Darya and Syr Darya rivers and encompassing key Silk Road cities such as Samarkand and Bukhara.
  • E. Oriente
    Oriente is a Bolivian professional football club based in Santa Cruz de la Sierra, known for competing in the country’s top division.
  • 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_69e0b4bb2b4081908fa4a72444120f35 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aada19e481909363428ceda67603 completed April 20, 2026, 10:38 p.m.
Created at: April 16, 2026, 11:41 a.m.