Triple
T2756867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jharkhand |
E61121
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Ranchi |
E181156
|
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: Ranchi | Statement: [Jharkhand, capital, Ranchi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ranchi Context triple: [Jharkhand, capital, Ranchi]
-
A.
Ranchi
chosen
Ranchi is the capital city of the Indian state of Jharkhand, known for its hilly terrain, waterfalls, and role as a regional political and commercial center.
-
B.
Raipur
Raipur is a major city in central India that serves as the commercial and administrative hub of the state of Chhattisgarh.
-
C.
Patna
Patna is the capital city of the Indian state of Bihar, situated along the Ganges River and known as one of the oldest continuously inhabited cities in the world.
-
D.
Gorakhpur
Gorakhpur is a prominent city in northern India known as a regional commercial, transportation, and cultural hub near the border with Nepal.
-
E.
Guwahati
Guwahati is a major city in northeastern India, serving as a key cultural, economic, and transportation hub for the region.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb8a292c8190ab3982434805241a |
completed | March 7, 2026, 8:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afbbdf650c8190baa020143b51f94b |
completed | March 10, 2026, 6:36 a.m. |
Created at: March 6, 2026, 9:56 p.m.