Triple
T26093799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gundicha Temple, Puri |
E658204
|
entity |
| Predicate | distanceFromJagannathTemple |
P194457
|
FINISHED |
| Object | approximately 3 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 3 kilometres | Statement: [Gundicha Temple, Puri, distanceFromJagannathTemple, approximately 3 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromJagannathTemple Context triple: [Gundicha Temple, Puri, distanceFromJagannathTemple, approximately 3 kilometres]
-
A.
distanceToBodhGaya
Indicates the spatial distance between a given entity and the location of Bodh Gaya.
-
B.
distanceToAyodhya
Indicates the measured spatial distance between a given entity’s location and the location of Ayodhya.
-
C.
distanceFromBhubaneswar
Indicates the spatial distance between a given entity and the location of Bhubaneswar.
-
D.
distanceFromNalandaRuins
Indicates the measured distance between a given entity and the Nalanda ruins.
-
E.
distanceFromVrindavan
Indicates the spatial distance between a given entity and the location Vrindavan.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: April 26, 2026, 7:49 p.m.