Triple
T19315628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ropar |
E483089
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Ropar |
—
|
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: Ropar | Statement: [Ropar, hasSpellingVariant, Ropar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ropar Context triple: [Ropar, hasSpellingVariant, Ropar]
-
A.
Ropar
chosen
Ropar is the former name of Rupnagar, a historic town in the Indian state of Punjab known for its archaeological significance and location on the banks of the Sutlej River.
-
B.
Gurgum
Gurgum was an Iron Age Neo-Hittite kingdom located in southeastern Anatolia, known from Assyrian records for its regional political and military significance.
-
C.
Tarn Taran
Tarn Taran is a historic town in the Majha region of Punjab, India, known for its significant Sikh religious heritage and prominent gurdwaras.
-
D.
Radwar
Radwar is a prominent Polish defense company known for developing and producing advanced radar and air-defense systems.
-
E.
Jagiroad
Jagiroad is a prominent industrial and commercial town in Assam, India, known especially for its paper mill and strategic location along key transport routes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d833034819092a8414d5e0fc26e |
completed | April 20, 2026, 11:26 a.m. |
Created at: April 10, 2026, 1:32 p.m.