Triple
T29845357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intangible cultural heritage of Bolivia |
E757915
|
entity |
| Predicate | isSafeguardedFor |
P15793
|
FINISHED |
| Object | future generations |
—
|
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: future generations | Statement: [Intangible cultural heritage of Bolivia, isSafeguardedFor, future generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSafeguardedFor Context triple: [Intangible cultural heritage of Bolivia, isSafeguardedFor, future generations]
-
A.
isProtectedFor
chosen
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
B.
safeguard
Indicates taking protective actions to shield someone or something from harm, loss, or danger.
-
C.
isSecureFor
Indicates that one entity provides a level of protection or safety that makes it appropriate or safe for use, access, or interaction by another entity.
-
D.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
isProtectedFrom
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760cbbcc81908cb6522f8eb38000 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:41 p.m.