Triple
T20168383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madanapalle |
E491886
|
entity |
| Predicate | distanceToTirupati |
P74721
|
FINISHED |
| Object | about 120 km (approximate by road) |
—
|
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 120 km (approximate by road) | Statement: [Madanapalle, distanceToTirupati, about 120 km (approximate by road)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTirupati Context triple: [Madanapalle, distanceToTirupati, about 120 km (approximate by road)]
-
A.
distanceFromTirupati
chosen
Indicates the measured distance between a given location and Tirupati.
-
B.
distanceToAyodhya
Indicates the measured spatial distance between a given entity’s location and the location of Ayodhya.
-
C.
distanceToPandharpur
Indicates the measured or estimated spatial distance between a given location and the place Pandharpur.
-
D.
distanceFromVrindavan
Indicates the spatial distance between a given entity and the location Vrindavan.
-
E.
distanceFromKumbakonam
Indicates the spatial distance between a given location and the reference location Kumbakonam.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66845cb588190820c50eea0c40d83 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.