Triple
T23144314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valsad |
E577543
|
entity |
| Predicate | distanceToSuratApproxKm |
P116603
|
FINISHED |
| Object | about 70 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: about 70 km | Statement: [Valsad, distanceToSuratApproxKm, about 70 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSuratApproxKm Context triple: [Valsad, distanceToSuratApproxKm, about 70 km]
-
A.
distanceToSurat
chosen
Indicates the measured distance between a given entity’s location and the city of Surat.
-
B.
distanceFromMumbaiApproxKm
Indicates the approximate physical distance, measured in kilometers, between a given location and Mumbai.
-
C.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
-
D.
distanceFromPune
Indicates the spatial distance between a given location or entity and the city of Pune.
-
E.
distanceToAhmedabad
Indicates the spatial distance between a given location or entity and the city of Ahmedabad.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecd40108190aaad7faf754b7936 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.