Triple
T19279441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phagwara |
E482147
|
entity |
| Predicate | distanceToJalandhar_km |
P57429
|
FINISHED |
| Object | approximately 20 |
—
|
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 20 | Statement: [Phagwara, distanceToJalandhar_km, approximately 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToJalandhar_km Context triple: [Phagwara, distanceToJalandhar_km, approximately 20]
-
A.
distanceToJalandharApproxKm
chosen
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and the city of Jalandhar.
-
B.
distanceToChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Chandigarh.
-
C.
distanceFromChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Chandigarh.
-
D.
distanceToJamshedpur_km
Indicates the physical distance, measured in kilometers, between a given location and Jamshedpur.
-
E.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbf817c819098745ed365cda4a9 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.