Triple
T34032188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackfoot Lakota |
E872684
|
entity |
| Predicate | hasModernIssues |
P40848
|
FINISHED |
| Object | language preservation |
—
|
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: language preservation | Statement: [Blackfoot Lakota, hasModernIssues, language preservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernIssues Context triple: [Blackfoot Lakota, hasModernIssues, language preservation]
-
A.
notableModernIssue
Indicates that the subject is recognized as a significant or widely discussed issue in contemporary times.
-
B.
hasOngoingIssues
Indicates that an entity is currently experiencing unresolved or continuing problems or difficulties.
-
C.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
D.
modernIssue
chosen
Indicates that the subject is a contemporary or current-day issue affecting the object or broader context.
-
E.
hasRecentIssue
Indicates that an entity is associated with an issue or problem that has occurred within a recent or specified time frame.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 1:51 a.m.