Triple
T32025527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muddenahalli |
E817806
|
entity |
| Predicate | distanceFromChikkaballapur |
P204053
|
FINISHED |
| Object | about 7 km |
—
|
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 7 km | Statement: [Muddenahalli, distanceFromChikkaballapur, about 7 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromChikkaballapur Context triple: [Muddenahalli, distanceFromChikkaballapur, about 7 km]
-
A.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
B.
distanceToBelagavi
Indicates the spatial distance between a given entity and the location of Belagavi.
-
C.
distanceFromBangalore
Indicates the spatial distance separating a given entity or location from Bangalore.
-
D.
distanceFromMadikeri
Indicates the spatial distance between a given location and Madikeri.
-
E.
distanceFromMangaluru_km
Indicates the distance, measured in kilometers, between a given place and Mangaluru.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a03142a3a7081909bcfb683b44e2217 |
completed | May 12, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_6a031400af808190a72abf095e96c151 |
completed | May 12, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_6a03142984848190b35c2636c73376af |
completed | May 12, 2026, 11:51 a.m. |
Created at: May 1, 2026, 12:17 a.m.