Triple
T11168636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangail |
E264218
|
entity |
| Predicate | distanceToDhaka |
P80017
|
FINISHED |
| Object | approximately 98 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 98 km | Statement: [Tangail, distanceToDhaka, approximately 98 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDhaka Context triple: [Tangail, distanceToDhaka, approximately 98 km]
-
A.
distanceToDhakaByRoadApproxKm
chosen
Indicates the approximate distance in kilometers between an entity and Dhaka when traveling by road.
-
B.
distanceToBangladeshBorder_km
Indicates the distance, measured in kilometers, from a given location to the nearest point on the border of Bangladesh.
-
C.
distanceFromKolkata
Indicates the spatial distance between a given location and the city of Kolkata.
-
D.
distanceFromGuwahati_km
Indicates the physical distance, measured in kilometers, between an entity and the location of Guwahati.
-
E.
distanceToSiliguri_km
Indicates the physical distance, measured in kilometers, between a given location and Siliguri.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.