Triple
T16138800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhiwani district |
E391598
|
entity |
| Predicate | administrativeSubdivisions |
P10770
|
FINISHED |
| Object | tehsils |
—
|
LITERAL 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: tehsils | Statement: [Bhiwani district, administrativeSubdivisions, tehsils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeSubdivisions Context triple: [Bhiwani district, administrativeSubdivisions, tehsils]
-
A.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
B.
countrySubdivision
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
-
C.
realmSubdivision
Indicates a hierarchical relationship where one realm is a constituent subdivision or part of a larger realm.
-
D.
politicalDivision
chosen
Indicates that one entity is a governmental or administrative subdivision or jurisdiction within the territory or authority of another entity.
-
E.
geographicDivision
Indicates that one place is an administrative or territorial subdivision of another place.
- F. None of above.
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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a06e0988190b5cd62d422d058a2 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.