Triple
T20088372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosan (disputed) |
E496197
|
entity |
| Predicate | languageFamilyIncluded |
P35117
|
FINISHED |
| Object | Salishan |
—
|
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: Salishan | Statement: [Mosan (disputed), languageFamilyIncluded, Salishan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyIncluded Context triple: [Mosan (disputed), languageFamilyIncluded, Salishan]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyOf
chosen
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
C.
languageFamilyCoverage
Indicates the extent to which a given entity (such as a resource, model, or system) supports or covers the languages within a specified language family.
-
D.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
E.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655c7de081909a400c736e92495d |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:17 p.m.