Triple
T16899680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladwa |
E424401
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Shahbad |
E1239300
|
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: Shahbad | Statement: [Ladwa, hasNearbyCity, Shahbad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shahbad Context triple: [Ladwa, hasNearbyCity, Shahbad]
-
A.
Shahhat
Shahhat is a town in northeastern Libya known for its proximity to the ancient Greek city of Cyrene and its location in the fertile Jabal al Akhdar region.
-
B.
Miranshah
Miranshah was a son of the Turco-Mongol conqueror Timur (Tamerlane) who served as one of his key governors and military commanders in the Timurid Empire.
-
C.
Miranshah
Miranshah is the main administrative and commercial town of North Waziristan in Pakistan’s Khyber Pakhtunkhwa province, near the border with Afghanistan.
-
D.
Shahabad
Shahabad is a town in Uttar Pradesh, India, situated within the administrative boundaries of Rampur district.
-
E.
Shahabad
chosen
Shahabad is a town in the Kurukshetra district of Haryana, India, known historically by its former name Shahbad Markanda.
- 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_6a00cfcd0db8819080d415a18b3435e2 |
completed | May 10, 2026, 6:34 p.m. |
Created at: April 10, 2026, 5:29 a.m.