Triple
T36495635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Channarayapatna |
E899177
|
entity |
| Predicate | belongsToDistrictHeadquarters |
P124424
|
FINISHED |
| Object | Hassan |
—
|
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: Hassan | Statement: [Channarayapatna, belongsToDistrictHeadquarters, Hassan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDistrictHeadquarters Context triple: [Channarayapatna, belongsToDistrictHeadquarters, Hassan]
-
A.
districtHeadquarterWithin
Indicates that the administrative headquarters of a district is located within the boundaries of a specified area or entity.
-
B.
nearestDistrictHeadquarters
Indicates that one location is the closest district headquarters to another specified place.
-
C.
hasParentDistrictHeadquarters
chosen
Indicates that an administrative district has a specific location designated as its parent (or main) district headquarters.
-
D.
belongsToDistrictLevelCity
Indicates that an entity is administratively part of, or falls under the jurisdiction of, a specific district-level city.
-
E.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:10 p.m.