Triple
T26263212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marapu ceremonies |
E656907
|
entity |
| Predicate | involvesPerformance |
P170629
|
FINISHED |
| Object | ritual dances |
—
|
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: ritual dances | Statement: [Marapu ceremonies, involvesPerformance, ritual dances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesPerformance Context triple: [Marapu ceremonies, involvesPerformance, ritual dances]
-
A.
performanceIncludes
chosen
Indicates that a performance encompasses, contains, or is composed of a specified component, act, segment, or element.
-
B.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
C.
performanceAs
Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving another entity.
-
D.
supportingPerformanceBy
Indicates that one performance serves as a supporting or secondary act that complements or enhances another primary performance.
-
E.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 9:10 p.m.