Triple
T22175813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakpak-Dairi |
E548045
|
entity |
| Predicate | hasNeighborLanguage |
P16383
|
FINISHED |
| Object | Gayo language |
—
|
NE NERFINISHED |
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: Gayo language | Statement: [Pakpak-Dairi, hasNeighborLanguage, Gayo language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gayo language Context triple: [Pakpak-Dairi, hasNeighborLanguage, Gayo language]
-
A.
Gayo language
chosen
The Gayo language is an Austronesian language spoken primarily by the Gayo people in the central highlands of Aceh, northern Sumatra, Indonesia.
-
B.
Garo language
The Garo language is a Tibeto-Burman language spoken primarily by the Garo people of northeastern India and neighboring Bangladesh.
-
C.
Buyi language
The Buyi language is a Tai–Kadai language spoken primarily by the Buyi ethnic group in Guizhou and neighboring regions of southern China.
-
D.
Batui language
The Batui language is an Austronesian language spoken in Central Sulawesi, Indonesia, and is part of the Saluan–Banggai subgroup.
-
E.
Baangi language
The Baangi language is a lesser-known Nupoid (Benue–Congo) language spoken by a small community in Nigeria.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6c40988190ba52ea46079eb306 |
completed | April 28, 2026, 9:45 p.m. |
Created at: April 16, 2026, 8:34 p.m.