Triple
T13661443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heggadadevanakote |
E327004
|
entity |
| Predicate | distanceToMysore |
P45594
|
FINISHED |
| Object | approximately 50 kilometres |
—
|
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: approximately 50 kilometres | Statement: [Heggadadevanakote, distanceToMysore, approximately 50 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMysore Context triple: [Heggadadevanakote, distanceToMysore, approximately 50 kilometres]
-
A.
distanceFromMysuru
chosen
Indicates the spatial distance between a given location and the city of Mysuru.
-
B.
distanceFromMadikeri
Indicates the spatial distance between a given location and Madikeri.
-
C.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
D.
distanceFromBangalore
Indicates the spatial distance separating a given entity or location from Bangalore.
-
E.
distanceToHyderabad
Indicates the spatial distance between a given entity’s location and the city of Hyderabad.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc620df208190afaccf3ddd10aa60 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.