Triple
T31441133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahidpur |
E802068
|
entity |
| Predicate | distanceToUjjain |
P203683
|
FINISHED |
| Object | approximately 56 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 56 kilometres | Statement: [Mahidpur, distanceToUjjain, approximately 56 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToUjjain Context triple: [Mahidpur, distanceToUjjain, approximately 56 kilometres]
-
A.
distanceToJodhpur
Indicates the spatial distance between a given entity or location and the city of Jodhpur.
-
B.
distanceFromJaipur
Indicates the spatial distance between a given entity and the location Jaipur.
-
C.
distanceToAyodhya
Indicates the measured spatial distance between a given entity’s location and the location of Ayodhya.
-
D.
distanceFromUdaipur
Indicates the spatial distance between a given location or entity and the city of Udaipur.
-
E.
distanceFromJabalpur
Indicates the spatial distance measured from the reference location Jabalpur to another place or entity.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01c5c5dbb881909b19ba87a7760ee7 |
completed | May 11, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_6a01c549af98819098e0effd775b7710 |
completed | May 11, 2026, 12:02 p.m. |
| PDg | Predicate description generation | batch_6a01c5c4da488190ab79ac9cfd9757fa |
completed | May 11, 2026, 12:04 p.m. |
Created at: April 30, 2026, 9:05 p.m.