Triple
T27497286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oyilattam |
E694050
|
entity |
| Predicate | danceStyleCharacteristic |
P103855
|
FINISHED |
| Object | synchronized group formations |
—
|
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: synchronized group formations | Statement: [Oyilattam, danceStyleCharacteristic, synchronized group formations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceStyleCharacteristic Context triple: [Oyilattam, danceStyleCharacteristic, synchronized group formations]
-
A.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
hasChoreographicCharacteristics
Indicates that something possesses specific features, qualities, or attributes related to choreography or choreographic style.
-
C.
danceFeature
chosen
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
D.
danceAbility
Indicates the level or quality of how well an entity can dance.
-
E.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:09 p.m.