Triple
T37752295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandhana |
E941013
|
entity |
| Predicate | distanceToKhandwaApprox |
P204374
|
FINISHED |
| Object | about 30 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 30 kilometres | Statement: [Pandhana, distanceToKhandwaApprox, about 30 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKhandwaApprox Context triple: [Pandhana, distanceToKhandwaApprox, about 30 kilometres]
-
A.
distanceToWardha
Indicates the spatial distance between a given entity and the location named Wardha.
-
B.
distanceToPandharpur
Indicates the measured or estimated spatial distance between a given location and the place Pandharpur.
-
C.
distanceToJalgaon_km
Indicates the physical distance, measured in kilometers, between an entity and the location Jalgaon.
-
D.
distanceToGondia_km
Indicates the physical distance, measured in kilometers, between a given location and Gondia.
-
E.
distanceToNagpur
Indicates the spatial distance between a given entity’s location and the city of Nagpur.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.