Triple
T21867920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virpur |
E539928
|
entity |
| Predicate | hasNameInEnglish |
P3437
|
FINISHED |
| Object | Virpur |
—
|
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: Virpur | Statement: [Virpur, hasNameInEnglish, Virpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Virpur Context triple: [Virpur, hasNameInEnglish, Virpur]
-
A.
Virpur
chosen
Virpur is a town in Gujarat, India, historically notable as the former capital of the princely Virpur State.
-
B.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
-
C.
Padampur
Padampur is a town in the Ganganagar district of Rajasthan, India, known for its agricultural economy supported by canal irrigation in the arid northwestern region of the state.
-
D.
Duhshala
Duhshala is the only daughter of King Dhritarashtra and Queen Gandhari in the Indian epic Mahabharata, known for her marriage to Jayadratha.
-
E.
Jetpur
Jetpur is a textile and dyeing hub town in Gujarat, India, known for its cotton saree printing and screen-printing industries.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33305d081908cd070134420607a |
completed | April 28, 2026, 5:49 p.m. |
Created at: April 16, 2026, 6:57 p.m.