Triple

T9487993
Position Surface form Disambiguated ID Type / Status
Subject Parun Valley E228810 entity
Predicate hasSettlement P1068 FINISHED
Object Parun E248496 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: Parun | Statement: [Parun Valley, hasSettlement, Parun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parun
Context triple: [Parun Valley, hasSettlement, Parun]
  • A. Parun chosen
    Parun is a small town in eastern Afghanistan that serves as the administrative and political center of Nuristan Province.
  • B. Poronin
    Poronin is a village in southern Poland’s Tatra region, known as a gateway to the Tatra Mountains and a base for tourism near Zakopane.
  • C. Parushni
    Parushni is the ancient Vedic name for the Ravi River, one of the major rivers of the northwestern Indian subcontinent.
  • D. Parmouti
    Parmouti is the eighth month of the ancient Egyptian and Coptic calendars, traditionally corresponding roughly to April in the Gregorian calendar.
  • E. Pujali
    Pujali is a small town and municipality in the Indian state of West Bengal, situated near Kolkata along the Hooghly River.
  • 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_69ca847424f081908180305555139f7a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd80c443b88190968d2092a73e1ee4 completed April 1, 2026, 8:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12d18fd908190b562fa0a8dad7c63 completed April 4, 2026, 3:24 p.m.
Created at: March 30, 2026, 7:55 p.m.