Triple
T37114439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mhasla |
E919079
|
entity |
| Predicate | isTalukaHeadquarters |
P139183
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mhasla, isTalukaHeadquarters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTalukaHeadquarters Context triple: [Mhasla, isTalukaHeadquarters, true]
-
A.
isTehsilHeadquarters
chosen
Indicates that a location serves as the administrative headquarters for a tehsil (sub-district) within an administrative division.
-
B.
hasTehsil
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
C.
hasParentDistrictHeadquarters
Indicates that an administrative district has a specific location designated as its parent (or main) district headquarters.
-
D.
districtHeadquarterWithin
Indicates that the administrative headquarters of a district is located within the boundaries of a specified area or entity.
-
E.
isCountyTown
Indicates that a town serves as the administrative or principal town of a specific county.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.