Triple
T1856973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mizoram |
E41724
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Aizawl |
E168300
|
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: Aizawl | Statement: [Mizoram, capital, Aizawl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aizawl Context triple: [Mizoram, capital, Aizawl]
-
A.
Aizawl
chosen
Aizawl is the hilly capital city of the Indian state of Mizoram, known for its scenic landscapes and vibrant Mizo culture in Northeast India.
-
B.
Imphal
Imphal is the capital city of the Indian state of Manipur, known for its scenic valleys, historic Kangla Fort, and cultural significance in Northeast India.
-
C.
Shillong
Shillong is the capital city of the northeastern Indian state of Meghalaya, known for its scenic hills, colonial-era architecture, and vibrant cultural life.
-
D.
Kohima
Kohima is the hilly capital city of Nagaland, known for its strategic role in World War II and its rich Naga cultural heritage.
-
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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb07fc5f08190a195a2f24d7b858a |
completed | March 7, 2026, 4:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3c82d50819094e8ccdba0faf819 |
completed | March 8, 2026, 10:10 p.m. |
Created at: March 4, 2026, 7:33 p.m.