Triple
T18971262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Kettles Lakota |
E464174
|
entity |
| Predicate | ethnologueLanguage |
P19233
|
FINISHED |
| Object | lkt |
—
|
LITERAL 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: lkt | Statement: [Two Kettles Lakota, ethnologueLanguage, lkt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnologueLanguage Context triple: [Two Kettles Lakota, ethnologueLanguage, lkt]
-
A.
hasEthnologueEntry
chosen
Indicates that there exists an entry for the subject in the Ethnologue language reference resource.
-
B.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
C.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
D.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
E.
languageContactWith
Indicates a relationship where two or more languages come into contact through their speakers, leading to interaction and potential mutual influence.
- F. None of above.
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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61a8bbc8190881908a71e0f2a53 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon