Triple
T9770863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimasa community |
E237119
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Dima |
E820059
|
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: Dima | Statement: [Dimasa community, alternativeName, Dima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dima Context triple: [Dimasa community, alternativeName, Dima]
-
A.
Dima
chosen
Dima is an alternative name for the Dimasa people, an indigenous ethnic group primarily inhabiting parts of Northeast India.
-
B.
Mila
Mila is a leading artificial intelligence research institute based in Quebec, renowned for its work in deep learning and machine learning.
-
C.
Misha
Misha is the bear mascot of the 1980 Moscow Summer Olympics, widely remembered for its iconic, sentimental farewell during the closing ceremony.
-
D.
Ilya
Ilya is a common Russian given name, notably borne by star ice hockey player Ilya Kovalchuk.
-
E.
Dimitri
Dimitri is a masculine given name of Greek origin, commonly used in various cultures and languages.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f329148190a5e531478bc18073 |
completed | April 1, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c4154af081908ca743b43ade83c7 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:26 p.m.