Triple
T18030000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenki culture |
E431358
|
entity |
| Predicate | contemporaryProcess |
P129518
|
FINISHED |
| Object | cultural revitalization efforts |
—
|
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: cultural revitalization efforts | Statement: [Evenki culture, contemporaryProcess, cultural revitalization efforts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryProcess Context triple: [Evenki culture, contemporaryProcess, cultural revitalization efforts]
-
A.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
B.
contemporaryFunction
Indicates that one entity serves a role or performs a function during the same time period as another entity.
-
C.
contemporaryTendency
Indicates that one entity reflects, aligns with, or exemplifies a prevailing trend, style, or tendency of the same time period as another entity.
-
D.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern context.
-
E.
contemporaryDescription
Indicates that one entity provides a description or account of another entity that is current or relevant to the same time period.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be347f6c8190b324fe74b7dc1764 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.