Triple
T4322473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Coast Penutian |
E96549
|
entity |
| Predicate | languageFamilyType |
P36135
|
FINISHED |
| Object | Amerindian (North America) |
—
|
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: Amerindian (North America) | Statement: [Oregon Coast Penutian, languageFamilyType, Amerindian (North America)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyType Context triple: [Oregon Coast Penutian, languageFamilyType, Amerindian (North America)]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
C.
languageFamilyAssociation
chosen
Indicates an association where one entity belongs to, is classified under, or is related to a particular language family.
-
D.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language family.
-
E.
languageFamilyCode
Indicates the language family to which a given language belongs, represented by a standardized code.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351177eb88190b89fa49a88add5e8 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.