Triple
T27895765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabiyari people |
E705484
|
entity |
| Predicate | ceremoniesCenteredOn |
P50686
|
FINISHED |
| Object | fertility and abundance |
—
|
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: fertility and abundance | Statement: [Cabiyari people, ceremoniesCenteredOn, fertility and abundance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremoniesCenteredOn Context triple: [Cabiyari people, ceremoniesCenteredOn, fertility and abundance]
-
A.
ceremonySignificance
Indicates the importance, meaning, or role that a particular ceremony holds within a given context or for specific participants.
-
B.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
C.
ceremonialFocus
chosen
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
-
D.
hasCeremonies
Indicates that an entity conducts, includes, or is associated with one or more formal ceremonies or ritual events.
-
E.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:38 p.m.