Triple
T30794922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koppal Assembly constituency |
E784201
|
entity |
| Predicate | isInSouthernIndia |
P117763
|
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: [Koppal Assembly constituency, isInSouthernIndia, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInSouthernIndia Context triple: [Koppal Assembly constituency, isInSouthernIndia, True]
-
A.
partlyLocatedInIndianState
Indicates that an entity is geographically or administratively situated such that only part of it lies within the boundaries of a specified Indian state.
-
B.
isInSubcontinent
chosen
Indicates that one entity (typically a place or region) is geographically located within the boundaries of a specified subcontinent.
-
C.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
D.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
-
E.
locatedOnDeccanPlateau
Indicates that the subject is geographically situated on the Deccan Plateau region.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690110f008190a1577560ed7790ed |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:42 p.m.