Triple
T18181950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Kʼicheʼ |
E435307
|
entity |
| Predicate | hasGlottocodeOfParentLanguage |
P3086
|
FINISHED |
| Object | kich1262 |
—
|
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: kich1262 | Statement: [Southern Kʼicheʼ, hasGlottocodeOfParentLanguage, kich1262]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlottocodeOfParentLanguage Context triple: [Southern Kʼicheʼ, hasGlottocodeOfParentLanguage, kich1262]
-
A.
hasGlottologEntry
Indicates that there exists a corresponding entry for the entity in the Glottolog linguistic database.
-
B.
hasGlottologName
Indicates that an entity is associated with a specific name as recorded in the Glottolog linguistic database.
-
C.
hasGlottologReference
Indicates that an entity is associated with a specific reference entry in the Glottolog linguistic database.
-
D.
glottocode
chosen
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
E.
hasPrimaryLanguageSubbranch
Indicates that one language subbranch is the main or principal subbranch associated with a given language or language family.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffb3bc88190a627be9c444d5c7d |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.