Triple
T16825290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranch House Party |
E409003
|
entity |
| Predicate | partOfBalletActStructure |
P34106
|
FINISHED |
| Object | Rodeo dance sequence |
—
|
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: Rodeo dance sequence | Statement: [Ranch House Party, partOfBalletActStructure, Rodeo dance sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBalletActStructure Context triple: [Ranch House Party, partOfBalletActStructure, Rodeo dance sequence]
-
A.
balletInActs
Indicates that a ballet is structured or divided into a specified number of acts.
-
B.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
-
C.
danceRole
Indicates that one entity has a specific role or function within a dance performed with or in relation to another entity.
-
D.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
E.
actStructure
chosen
Indicates a structural or organizational relationship that defines how an action or activity is arranged, composed, or internally organized.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3126db88190ac5595b0d50e4232 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.