Triple
T5353704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandi district |
E102636
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Mandeali |
E334808
|
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: Mandeali | Statement: [Mandi district, language, Mandeali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mandeali Context triple: [Mandi district, language, Mandeali]
-
A.
Mandeali
chosen
Mandeali is an Indo-Aryan language spoken primarily in the Mandi district of Himachal Pradesh in northern India.
-
B.
Mandinka
Mandinka is a major Mande language spoken primarily in The Gambia, Senegal, Guinea-Bissau, and neighboring West African countries by the Mandinka people.
-
C.
Kandia
Kandia is a remote valley and settlement area located within Pakistan’s Kohistan mountain ranges, known for its rugged terrain and isolated communities.
-
D.
Mokena
Mokena is a suburban village in Will County, Illinois, located southwest of Chicago.
-
E.
Duitama
Duitama is a Colombian city in the Andean highlands known as an important commercial and transport hub within the Boyacá 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86149774819084049a8785e3f2e0 |
completed | March 20, 2026, 5:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21dbc540819086aca16af1aa6213 |
completed | March 21, 2026, 10:55 p.m. |
Created at: March 20, 2026, 2:01 p.m.