Triple
T28886398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayhto Bo festival |
E732571
|
entity |
| Predicate | hasIntangibleAspect |
P119562
|
FINISHED |
| Object | beliefs about ancestors |
—
|
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: beliefs about ancestors | Statement: [Kayhto Bo festival, hasIntangibleAspect, beliefs about ancestors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntangibleAspect Context triple: [Kayhto Bo festival, hasIntangibleAspect, beliefs about ancestors]
-
A.
hasIntangibleHeritageAspect
chosen
Indicates that something possesses or is associated with a non-physical cultural or heritage-related quality, practice, or tradition.
-
B.
areIntangible
Indicates that the related entities lack physical substance and cannot be perceived through the senses as material objects.
-
C.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
D.
possibleAspect
Indicates that one entity can be viewed as a potential aspect, facet, or component of another entity.
-
E.
nonMaterialAspect
Indicates that one entity represents an immaterial, intangible, or conceptual aspect or property of another entity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: April 28, 2026, 7:50 a.m.