Triple
T35648132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokan hypothesis |
E1030063
|
entity |
| Predicate | concernsLanguages |
P46510
|
FINISHED |
| Object | Native American languages |
—
|
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: Native American languages | Statement: [Hokan hypothesis, concernsLanguages, Native American languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsLanguages Context triple: [Hokan hypothesis, concernsLanguages, Native American languages]
-
A.
primaryLanguageConcerned
Indicates that the relationship or action specifically involves or pertains to the main or principal language in question.
-
B.
languageFamilyConcerned
chosen
Indicates that something is related to, involves, or pertains to a particular language family.
-
C.
focusesOnLanguage
Indicates that an entity’s primary attention, activity, or content is directed toward language as its main subject or concern.
-
D.
affectedLanguage
Indicates that one entity has an effect on, modifies, or influences the state, usage, or characteristics of a particular language.
-
E.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.