Triple
T34074085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nutbush line dance |
E873855
|
entity |
| Predicate | hasDirectionChanges |
P198710
|
FINISHED |
| Object | quarter turns |
—
|
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: quarter turns | Statement: [Nutbush line dance, hasDirectionChanges, quarter turns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionChanges Context triple: [Nutbush line dance, hasDirectionChanges, quarter turns]
-
A.
hasDirectionVariability
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
B.
hasDirectionVariant
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
C.
hasNumberOfDirections
Indicates that an entity is associated with a specific count of possible directions or orientations.
-
D.
hasDriftDirection
Indicates that an entity’s motion or displacement occurs predominantly in a specified direction.
-
E.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
- F. None of above. chosen
Provenance (4 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: May 1, 2026, 1:52 a.m.