Triple
T4958183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rupnagar |
E111337
|
entity |
| Predicate | distanceFromChandigarh |
P50600
|
FINISHED |
| Object | approximately 45 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 45 km | Statement: [Rupnagar, distanceFromChandigarh, approximately 45 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromChandigarh Context triple: [Rupnagar, distanceFromChandigarh, approximately 45 km]
-
A.
distanceFromChandigarh_km
chosen
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Chandigarh.
-
B.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
-
C.
distanceToJalandharApproxKm
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and the city of Jalandhar.
-
D.
distanceFromIslamabad
Indicates the spatial distance between a given location and the city of Islamabad.
-
E.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d834c0819087f3faafdc9b4228 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.