Triple

T17809705
Position Surface form Disambiguated ID Type / Status
Subject Lahaul E444664 entity
Predicate hasSettlement P1068 FINISHED
Object Tandi 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: Tandi | Statement: [Lahaul, hasSettlement, Tandi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tandi
Context triple: [Lahaul, hasSettlement, Tandi]
  • A. Tandi chosen
    Tandi is a small town in Himachal Pradesh, India, known as a key junction in the Lahaul region where major mountain rivers meet and as a common stopover for travelers in the Himalayas.
  • B. Tandi
    Tandi is a small rural settlement located in Makoni District in eastern Zimbabwe.
  • C. Tantamani
    Tantamani was a Kushite king of the 25th Dynasty of Egypt, known for his brief attempt to restore Nubian control over Egypt before being driven back by the Assyrians.
  • D. Tanunda
    Tanunda is a prominent town in South Australia's Barossa Valley wine region, known for its rich German heritage and surrounding vineyards.
  • E. Tangale
    Tangale is a West Chadic language spoken primarily in Gombe State, northeastern Nigeria, by the Tangale people.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4887a50488190b9c148146ec607e6 completed April 19, 2026, 7:47 a.m.
Created at: April 10, 2026, 10:14 a.m.