Triple
T11027477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wôpanâôt8âôk |
E260663
|
entity |
| Predicate | languageRevivalStart |
P97358
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Wôpanâôt8âôk, languageRevivalStart, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageRevivalStart Context triple: [Wôpanâôt8âôk, languageRevivalStart, late 20th century]
-
A.
languageRevived
Indicates that a previously endangered or no-longer-spoken language has been brought back into active use within a community.
-
B.
languageRevivalMethod
Indicates the method or strategy used to revive or revitalize a language that is endangered, dormant, or no longer actively spoken.
-
C.
hasLanguageRevitalizationEfforts
Indicates that there are organized actions or initiatives aimed at preserving, strengthening, or reviving the use of a particular language.
-
D.
languageBegins
Indicates that a particular language starts to be used, recognized, or becomes relevant at a specific point in time or context.
-
E.
languageReform
Indicates efforts or actions aimed at changing, standardizing, or improving aspects of a language, such as its spelling, grammar, or usage rules.
- F. None of above. chosen
Provenance (4 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797d190f08190bcb5949ee24306f1 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:25 p.m.