Triple
T16899681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladwa |
E424401
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Yamunanagar |
E111942
|
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: Yamunanagar | Statement: [Ladwa, hasNearbyCity, Yamunanagar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yamunanagar Context triple: [Ladwa, hasNearbyCity, Yamunanagar]
-
A.
Yamunanagar
chosen
Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
-
B.
Saharanpur
Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
-
C.
Bhiwani
Bhiwani is a city in the Indian state of Haryana known as a regional educational and political hub.
-
D.
Raisinghnagar
Raisinghnagar is a town and administrative center in the northern Indian state of Rajasthan, known for its agricultural economy within the arid region near the India–Pakistan border.
-
E.
Jaunsar-Bawar
Jaunsar-Bawar is a hilly, culturally distinct region in Uttarakhand, India, known for its Jaunsari-speaking communities, traditional architecture, and unique customs.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dbc6e48190be90066b82fc61db |
completed | April 18, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01413843ec8190b4205aa5fdce28e5 |
completed | May 11, 2026, 2:38 a.m. |
Created at: April 10, 2026, 5:29 a.m.