Triple
T4431969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mula River |
E95350
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object | Aundh Bridge |
E442452
|
NE 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: Aundh Bridge | Statement: [Mula River, hasBridge, Aundh Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aundh Bridge Context triple: [Mula River, hasBridge, Aundh Bridge]
-
A.
Aundh Bridge
chosen
Aundh Bridge is a roadway bridge in Pune, India, that serves as a key connector across the Mula River between the Aundh area and surrounding localities.
-
B.
Chaderghat Bridge
Chaderghat Bridge is a major road bridge in Hyderabad, India, that serves as an important connector across the Musi River within the city.
-
C.
Khadki Bridge
Khadki Bridge is a roadway bridge in Pune, India, that serves as an important crossing and traffic link over the Mula River.
-
D.
Tista Bridge
Tista Bridge is a major roadway bridge spanning the Teesta River, serving as an important transport link in the surrounding region.
-
E.
Neelum Bridge
Neelum Bridge is a prominent road bridge spanning the Neelum River in Muzaffarabad, Azad Jammu and Kashmir, serving as a key local transportation link and landmark.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556cd83881908547aa311c4f17fa |
completed | March 13, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b65f34df20819090767fe4c577be87 |
completed | March 15, 2026, 7:26 a.m. |
Created at: March 12, 2026, 11:31 p.m.