Triple
T34734902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranakpur |
E1001311
|
entity |
| Predicate | distanceFromJodhpur |
P108565
|
FINISHED |
| Object | approximately 160 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: approximately 160 km | Statement: [Ranakpur, distanceFromJodhpur, approximately 160 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromJodhpur Context triple: [Ranakpur, distanceFromJodhpur, approximately 160 km]
-
A.
distanceToJodhpur
chosen
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.
distanceFromJabalpur
Indicates the spatial distance measured from the reference location Jabalpur to another place or entity.
-
D.
distanceFromJaisalmer
Indicates the measured spatial distance between a given entity and the location of Jaisalmer.
-
E.
distanceFromUdaipur
Indicates the spatial distance between a given location or entity and the city of Udaipur.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.