Triple

T22734394
Position Surface form Disambiguated ID Type / Status
Subject Lar E562224 entity
Predicate historicalRegion P915 FINISHED
Object Larestan 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: Larestan | Statement: [Lar, historicalRegion, Larestan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Larestan
Context triple: [Lar, historicalRegion, Larestan]
  • A. Larestan chosen
    Larestan is a county in southern Iran known for its historic towns, distinct local culture, and position within the broader Fars cultural region.
  • B. Sarvestan
    Sarvestan is a historic city in southern Iran known for its ancient Sassanid-era palace and archaeological sites.
  • C. Alasht
    Alasht is a small mountainous town in Mazandaran Province in northern Iran, best known as the birthplace of Reza Shah Pahlavi.
  • D. Dorostol
    Dorostol is the ancient name of the city now known as Silistra, a historically significant settlement on the Danube in northeastern Bulgaria.
  • E. Bavanat
    Bavanat is a small city in southern Iran known for its traditional rural landscapes, gardens, and location within the mountainous region of Fars Province.
  • 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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1796e4970819090fb9c9926673938 completed April 29, 2026, 3:22 a.m.
Created at: April 17, 2026, 3:22 p.m.