Triple
T36781276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhaka–Tangail Highway |
E908774
|
entity |
| Predicate | terminusDistrict |
P189373
|
FINISHED |
| Object | Tangail District |
—
|
NE NERFINISHED |
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: Tangail District | Statement: [Dhaka–Tangail Highway, terminusDistrict, Tangail District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusDistrict Context triple: [Dhaka–Tangail Highway, terminusDistrict, Tangail District]
-
A.
terminusBorough
Indicates the borough in which the endpoint or terminus of something (such as a route or line) is located.
-
B.
terminusCityArea
Indicates that a city area serves as the terminal or end-point location for a route, line, or journey.
-
C.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
D.
terminusWestBorough
Indicates that something serves as the western terminus or endpoint of a route, line, or connection at a place called Borough.
-
E.
terminusLocatedOn
Indicates that the endpoint or final stop of one entity (such as a route or line) is situated on or at another entity (such as a street, line, or location).
- F. None of above. chosen
Provenance (4 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:12 p.m.