Triple
T4265002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinulog Festival |
E96803
|
entity |
| Predicate | danceMovement |
P8577
|
FINISHED |
| Object | two steps forward and one step backward |
—
|
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: two steps forward and one step backward | Statement: [Sinulog Festival, danceMovement, two steps forward and one step backward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceMovement Context triple: [Sinulog Festival, danceMovement, two steps forward and one step backward]
-
A.
danceForm
Indicates that one entity is a style or type of dance associated with the other entity.
-
B.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
C.
danceCreated
Indicates that one entity is the creator or choreographer of a particular dance or dance work.
-
D.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
-
E.
dancePattern
chosen
Indicates a recurring or structured way in which an entity performs or organizes a dance or sequence of dance movements.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fcad0a881908e1cac0a6da5a321 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.