Triple
T6449961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhule district |
E139836
|
entity |
| Predicate | administrativeSubdivision |
P44156
|
FINISHED |
| Object | talukas |
—
|
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: talukas | Statement: [Dhule district, administrativeSubdivision, talukas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeSubdivision Context triple: [Dhule district, administrativeSubdivision, talukas]
-
A.
governingSubdivision
Indicates that one administrative or political unit serves as the governing authority over a smaller, subordinate territorial subdivision.
-
B.
governingCountrySubdivision
Indicates that one country subdivision (such as a state, province, or region) has governing authority or administrative control over another geographic or political area.
-
C.
countrySubdivision
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
-
D.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
administrativeDistricts
chosen
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b2c7bc81908c683ec22cad9628 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:47 p.m.