Triple
T15562659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Awaswas language |
E371035
|
entity |
| Predicate | hasLinguisticRelation |
P10003
|
FINISHED |
| Object | Karkin language |
E370145
|
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: Karkin language | Statement: [Awaswas language, hasLinguisticRelation, Karkin language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karkin language Context triple: [Awaswas language, hasLinguisticRelation, Karkin language]
-
A.
Karkin language
chosen
The Karkin language is an extinct Ohlone (Costanoan) Native American language once spoken in the San Francisco Bay Area of California.
-
B.
Karkar-Yuri language
Karkar-Yuri is a Papuan language of Papua New Guinea, spoken by the Karkar and Yuri peoples in the Sepik region.
-
C.
Karao language
The Karao language is an Austronesian language spoken by the Karao people in the Cordillera region of northern Luzon in the Philippines.
-
D.
Kairak language
The Kairak language is a Papuan language spoken by the Baining people of New Britain in Papua New Guinea.
-
E.
Kitharaka language
The Kitharaka language is a Bantu language spoken by the Tharaka people of Kenya, closely related to neighboring Kamba and Meru varieties.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddc66448190948280fb0c8d390c |
completed | April 16, 2026, 2:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff456821988190971539b683f6c656 |
completed | May 9, 2026, 2:32 p.m. |
Created at: April 10, 2026, 4:09 a.m.