Triple
T11628616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamkaur |
E276336
|
entity |
| Predicate | distanceToChandigarh |
P50600
|
FINISHED |
| Object | approximately 40 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 40 km | Statement: [Chamkaur, distanceToChandigarh, approximately 40 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChandigarh Context triple: [Chamkaur, distanceToChandigarh, approximately 40 km]
-
A.
distanceFromChandigarh_km
chosen
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Chandigarh.
-
B.
distanceToJalandharApproxKm
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and the city of Jalandhar.
-
C.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
-
D.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
-
E.
distanceToAmritsarApproxKm
Indicates an approximate physical distance, measured in kilometers, between a given entity’s location and the city of Amritsar.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1259cd08190a75eeacb5e39b858 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.