Triple
T9051157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arem |
E216884
|
entity |
| Predicate | culturalThreats |
P49657
|
FINISHED |
| Object | deforestation |
—
|
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: deforestation | Statement: [Arem, culturalThreats, deforestation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalThreats Context triple: [Arem, culturalThreats, deforestation]
-
A.
culturalIssue
Indicates that something pertains to, arises from, or significantly affects the beliefs, values, practices, or norms of a particular culture or group.
-
B.
heritageThreat
chosen
Indicates that an entity poses a risk of damage, loss, or degradation to cultural, historical, or natural heritage.
-
C.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
D.
culturalThemes
Indicates that there is a relationship between entities where one embodies, expresses, or is associated with particular cultural themes present in or derived from the other.
-
E.
culturalEmphasis
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b54423081908d9fd985109e336a |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.