Triple
T15945180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dizi |
E386665
|
entity |
| Predicate | hasNeighborLanguage |
P16383
|
FINISHED |
| Object | Me'en |
E1185217
|
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: Me'en | Statement: [Dizi, hasNeighborLanguage, Me'en]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Me'en Context triple: [Dizi, hasNeighborLanguage, Me'en]
-
A.
Me'en
chosen
Me'en is an Omotic language spoken primarily by the Me'en people of southwestern Ethiopia.
-
B.
Meent
Meent is a tram stop on Amsterdam’s Amstelveenlijn serving the residential area of Amstelveen in the Netherlands.
-
C.
Mehinako
Mehinako are an Indigenous people of the Upper Xingu region in Brazil, known for their distinct language, rich ritual traditions, and communal village life in the Amazon.
-
D.
Meya
Meya is a variant form of the given name Maya, often used as a feminine personal name.
-
E.
Mien
Mien are an ethnic group of the Yao minority in East and Southeast Asia, known for their distinct language, traditional dress, and mountain village communities.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d0d55c8190af59ff169e8add78 |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3bfe72c819095f40a255bcd7ad5 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.