Triple
T30069553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonk |
E764139
|
entity |
| Predicate | distanceToJaipurApproxKm |
P29700
|
FINISHED |
| Object | about 95 |
—
|
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 95 | Statement: [Tonk, distanceToJaipurApproxKm, about 95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToJaipurApproxKm Context triple: [Tonk, distanceToJaipurApproxKm, about 95]
-
A.
distanceFromJaipur
chosen
Indicates the spatial distance between a given entity and the location Jaipur.
-
B.
distanceToJodhpur
Indicates the spatial distance between a given entity or location and the city of Jodhpur.
-
C.
distanceFromJaisalmer
Indicates the measured spatial distance between a given entity and the location of Jaisalmer.
-
D.
distanceFromJabalpur
Indicates the spatial distance measured from the reference location Jabalpur to another place or entity.
-
E.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00cbae75988190974f5b45a2e62326 |
completed | May 10, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_6a00cabe4c5881909cca5efbe494e0d1 |
completed | May 10, 2026, 6:13 p.m. |
Created at: April 29, 2026, 7 p.m.