Triple
T16259793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karo Highlands |
E394723
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Karo language |
E511956
|
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: Karo language | Statement: [Karo Highlands, hasLanguage, Karo language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karo language Context triple: [Karo Highlands, hasLanguage, Karo language]
-
A.
Karo language
chosen
Karo language is an Austronesian language spoken by the Karo Batak people of North Sumatra, Indonesia.
-
B.
Karo language
Karo language is an indigenous Tupian language spoken by the Karo people of the Brazilian Amazon, known for its endangered status and significance in studies of South American linguistic diversity.
-
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.
Karkin language
The Karkin language is an extinct Ohlone (Costanoan) Native American language once spoken in the San Francisco Bay Area of California.
-
E.
Karata language
The Karata language is a Northeast Caucasian language spoken by the Karata people in the Republic of Dagestan, Russia.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c3082c8190a1c9f92b255fdbb6 |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000eee110c819088d99b80435ab70b |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.