Triple
T19708768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theur |
E473284
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Haveli taluka |
—
|
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: Haveli taluka | Statement: [Theur, locatedIn, Haveli taluka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haveli taluka Context triple: [Theur, locatedIn, Haveli taluka]
-
A.
Haveli taluka
chosen
Haveli taluka is an administrative subdivision in Pune district of Maharashtra, India, encompassing both urban and rural areas around the city of Pune.
-
B.
Mahuva taluka
Mahuva taluka is an administrative sub-division (taluka) in the Surat district of the Indian state of Gujarat.
-
C.
Ashti taluka
Ashti taluka is an administrative sub-division (tehsil) in the Wardha district of Maharashtra, India, comprising a group of villages and local governing bodies.
-
D.
Mandvi taluka
Mandvi taluka is an administrative subdivision (taluka) within Surat district in the state of Gujarat, India.
-
E.
Balasinor Taluka
Balasinor Taluka is an administrative subdivision in the Mahisagar district of Gujarat, India, known for encompassing the town of Balasinor and nearby rural areas.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642bc754481908bdf5bfad069aec8 |
completed | April 20, 2026, 3:14 p.m. |
Created at: April 10, 2026, 1:46 p.m.