Triple
T26140323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thuraiyur |
E659497
|
entity |
| Predicate | distanceFrom Tiruchirappalli |
P194844
|
FINISHED |
| Object | approximately 50–60 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 50–60 kilometres | Statement: [Thuraiyur, distanceFrom Tiruchirappalli, approximately 50–60 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFrom Tiruchirappalli Context triple: [Thuraiyur, distanceFrom Tiruchirappalli, approximately 50–60 kilometres]
-
A.
distanceFromChennai
Indicates the spatial distance between a given entity or location and the city of Chennai.
-
B.
distanceFromTirupati
Indicates the measured distance between a given location and Tirupati.
-
C.
distanceFromChittoor
Indicates the spatial distance between a given location and the reference location Chittoor.
-
D.
distanceToKanyakumari
Indicates the spatial distance between a given location and Kanyakumari.
-
E.
distanceFromKumbakonam
Indicates the spatial distance between a given location and the reference location Kumbakonam.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: April 26, 2026, 8:19 p.m.