Triple
T9326350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheek to Cheek ballroom dance |
E224394
|
entity |
| Predicate | includesElementsOf |
P11236
|
FINISHED |
| Object | foxtrot basic patterns |
—
|
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: foxtrot basic patterns | Statement: [Cheek to Cheek ballroom dance, includesElementsOf, foxtrot basic patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesElementsOf Context triple: [Cheek to Cheek ballroom dance, includesElementsOf, foxtrot basic patterns]
-
A.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
B.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
C.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
D.
areSupersetOf
Indicates that one set contains all elements of another set, possibly along with additional elements.
-
E.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f88e988190bb896a3d7c3c723c |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.