Triple
T6852774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cup’ig people |
E158061
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Cup’ig language |
E148361
|
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: Cup’ig language | Statement: [Cup’ig people, language, Cup’ig language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cup’ig language Context triple: [Cup’ig people, language, Cup’ig language]
-
A.
Cupeno language
The Cupeño language is an endangered Uto-Aztecan language historically spoken by the Cupeño people of Southern California.
-
B.
Kavalan language
The Kavalan language is an endangered Austronesian language of the indigenous Kavalan people of northeastern Taiwan.
-
C.
Cup’ig dialect
chosen
The Cup’ig dialect is a Central Alaskan Yupik variety traditionally spoken by the Cup’ig people of Nunivak Island in Alaska.
-
D.
Chumburung language
The Chumburung language is a Niger-Congo language spoken primarily by the Chumburung people in Ghana.
-
E.
Piipaash language
The Piipaash language is a Native American language of the Yuman family traditionally spoken by the Piipaash (Maricopa) people of the lower Colorado River region in the southwestern United States.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84fffbc8190943ca7f3f03937e9 |
completed | March 27, 2026, 7:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c72fd79e508190b00e45f9cceb3e21 |
completed | March 28, 2026, 1:33 a.m. |
Created at: March 27, 2026, 2:20 p.m.