Triple
T29235381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cofán language |
E741178
|
entity |
| Predicate | hasVitality |
P181144
|
FINISHED |
| Object | threatened intergenerational transmission |
—
|
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: threatened intergenerational transmission | Statement: [Cofán language, hasVitality, threatened intergenerational transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVitality Context triple: [Cofán language, hasVitality, threatened intergenerational transmission]
-
A.
isVigorous
Indicates that an entity exhibits strong energy, intensity, or forcefulness in its actions or behavior.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasRevitalizationMovement
Indicates that there exists an organized effort or movement aimed at renewing, restoring, or reinvigorating the subject entity.
-
D.
hasVictoriousPower
Indicates that one entity possesses a power, force, or capability that triumphs over opposition or competing entities.
-
E.
isLiving
Indicates that an entity is currently alive or possesses life.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 28, 2026, 12:29 p.m.