Triple
T29369067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khanapur |
E744802
|
entity |
| Predicate | distanceToBelagavi |
P202436
|
FINISHED |
| Object | about 26 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: about 26 kilometres | Statement: [Khanapur, distanceToBelagavi, about 26 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBelagavi Context triple: [Khanapur, distanceToBelagavi, about 26 kilometres]
-
A.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
B.
distanceFromBangalore
Indicates the spatial distance separating a given entity or location from Bangalore.
-
C.
approxDistanceToDharwad
Indicates that one entity is located at an approximate distance from the reference location Dharwad.
-
D.
distanceFromMangaluru_km
Indicates the distance, measured in kilometers, between a given place and Mangaluru.
-
E.
distanceFromMadikeri
Indicates the spatial distance between a given location and Madikeri.
- F. None of above. chosen
Provenance (4 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_6a007fc8f9f88190b78cd2ef3fc9c6fc |
completed | May 10, 2026, 12:53 p.m. |
Created at: April 28, 2026, 2:25 p.m.