Triple
T21245439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabarkantha district |
E523594
|
entity |
| Predicate | formerHeadquarters |
P22165
|
FINISHED |
| Object | Idar |
—
|
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: Idar | Statement: [Sabarkantha district, formerHeadquarters, Idar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Idar Context triple: [Sabarkantha district, formerHeadquarters, Idar]
-
A.
Idar State
chosen
Idar State was a princely state in western India during the British Raj, located in present-day Gujarat.
-
B.
Heidal
Heidal is a village in Innlandet county, Norway, known for its traditional wooden architecture and scenic location in the Gudbrandsdalen valley.
-
C.
Idarwald
Idarwald is a forested low mountain range in western Germany, known as part of the Hunsrück highlands.
-
D.
Eidså
Eidså is a small village in Vanylven Municipality in Møre og Romsdal county, Norway.
-
E.
Verdal
Verdal is a municipality in central Norway known for its agricultural landscape, industrial activity, and the historic battlefield of Stiklestad.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73599e5548190ad70d2c2bfa9e919 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 3:47 p.m.