Triple
T3003180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumiai |
E81836
|
entity |
| Predicate | hasGlottologName |
P6521
|
FINISHED |
| Object | Kumiai |
E81836
|
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: Kumiai | Statement: [Kumiai, hasGlottologName, Kumiai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kumiai Context triple: [Kumiai, hasGlottologName, Kumiai]
-
A.
Kumiai
chosen
Kumiai is an indigenous Yuman language spoken by the Kumeyaay people in the border region of southern California and northern Baja California.
-
B.
Kamiyama
Kamiyama is a Japanese surname borne by various individuals, including artists, athletes, and public figures.
-
C.
Ikoma
Ikoma is a city in Japan known for its scenic setting on the slopes of Mount Ikoma and its role as a residential and commuter hub near Osaka and Nara.
-
D.
Shimaore
Shimaore is a Bantu language closely related to Comorian, widely spoken by the local population of Mayotte in the Indian Ocean.
-
E.
Kubashima
Kubashima is one of the small, uninhabited islets that make up the disputed Senkaku Islands in the East China Sea.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1371c481909e214234afed1a65 |
completed | March 8, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44ec8df7081908dccdb36b7d1ca53 |
completed | March 13, 2026, 5:52 p.m. |
Created at: March 8, 2026, 2:59 p.m.