Triple
T19525728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washoe language |
E488512
|
entity |
| Predicate | neighboringLanguageRegion |
P16383
|
FINISHED |
| Object | Northern Paiute language area |
—
|
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: Northern Paiute language area | Statement: [Washoe language, neighboringLanguageRegion, Northern Paiute language area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringLanguageRegion Context triple: [Washoe language, neighboringLanguageRegion, Northern Paiute language area]
-
A.
hasNeighboringLanguages
chosen
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
-
B.
neighboringRegion
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
C.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
D.
neighboringLanguageFamilies
Indicates that two language families are geographically adjacent or border each other in their primary regions of use.
-
E.
hasSuccessorLanguageInRegion
Indicates that one language is followed or replaced by another language within a specific geographic region.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363aeb8c8190be2bdd73e421af96 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.