Triple
T30785089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaga |
E783934
|
entity |
| Predicate | hasDialectsCollectivelyCalled |
P4251
|
FINISHED |
| Object | Kichaga |
—
|
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: Kichaga | Statement: [Chaga, hasDialectsCollectivelyCalled, Kichaga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectsCollectivelyCalled Context triple: [Chaga, hasDialectsCollectivelyCalled, Kichaga]
-
A.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
B.
hasDialects
chosen
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
C.
hasDialectCluster
Indicates that one language or linguistic variety is associated with a particular group or cluster of related dialects.
-
D.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
E.
hasDialectChainWith
Indicates that two language varieties are connected through a continuous sequence of mutually intelligible dialects forming a dialect chain.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 8:41 p.m.