Triple
T3264124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaitpur |
E68481
|
entity |
| Predicate | hasCapital |
P204
|
FINISHED |
| Object | Jaitpur (town) |
E68481
|
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: Jaitpur (town) | Statement: [Jaitpur, hasCapital, Jaitpur (town)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaitpur (town) Context triple: [Jaitpur, hasCapital, Jaitpur (town)]
-
A.
Jaitpur
chosen
Jaitpur was a princely state in central India that was incorporated into British-controlled territory in the 19th century under the controversial Doctrine of Lapse policy.
-
B.
Jagdishpur
Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
-
C.
Madhepur
Madhepur is a town located in the Madhubani district of the Indian state of Bihar.
-
D.
Vikrampur
Vikrampur was a historic urban and political center in the Bengal region, renowned as an important seat of power and culture in medieval South Asia.
-
E.
Rajpura
Rajpura is an industrial and commercial town in the Patiala district of Punjab, India, known for its manufacturing base and strategic location as a transport hub.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcb2da08190a7f4fefdfe6d0098 |
completed | March 8, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b28ee82a78819082582a24bac97f44 |
completed | March 12, 2026, 10:01 a.m. |
Created at: March 8, 2026, 3:09 p.m.