Triple
T22150357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sureq Galigo |
E547395
|
entity |
| Predicate | traditionalPerformers |
P82018
|
FINISHED |
| Object | bissu priests |
—
|
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: bissu priests | Statement: [Sureq Galigo, traditionalPerformers, bissu priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPerformers Context triple: [Sureq Galigo, traditionalPerformers, bissu priests]
-
A.
traditionalPerformer
chosen
Indicates that an entity performs or practices traditional, culturally inherited arts, rituals, or performances.
-
B.
traditionalPerformerCommunity
Indicates a relationship in which a performer is associated with, belongs to, or is recognized as part of a community that practices traditional or culturally inherited performance arts.
-
C.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
D.
performingMusicians
Indicates that certain musicians are actively giving a performance, typically in association with a specific event, work, or venue.
-
E.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f37dac8190a7cecb12f4271515 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.