Triple

T20931139
Position Surface form Disambiguated ID Type / Status
Subject Turanians E515472 entity
Predicate mythologicalRegion P60644 FINISHED
Object Turan 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: Turan | Statement: [Turanians, mythologicalRegion, Turan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Turan
Context triple: [Turanians, mythologicalRegion, Turan]
  • A. Turan chosen
    Turan is a legendary land and people in Persian mythology and epic literature, often portrayed as the arch-enemies of Iran in works like the Shahnameh.
  • B. Turan
    Turan is the Etruscan goddess of love, beauty, and fertility, often associated with the Greek Aphrodite.
  • C. Touqan
    Touqan is a family name of notable Palestinian origin, associated with prominent poets, politicians, and intellectuals in the Arab world.
  • D. Almalyk
    Almalyk is a historic Central Asian city, now located in southeastern Kazakhstan, that was once an important Silk Road trading center.
  • E. Qarluq
    Qarluq refers to a historical Turkic tribal confederation that played a key role in Central Asian politics and the formation of early Turkic states.
  • 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_69e0b4fb431c8190b9d40e6a72f0cc87 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f6557e4881909ce932c3f538304a completed April 21, 2026, 4 a.m.
Created at: April 16, 2026, 12:49 p.m.