Triple
T31842639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dabke |
E812847
|
entity |
| Predicate | handConnection |
P172658
|
FINISHED |
| Object | dancers hold hands |
—
|
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: dancers hold hands | Statement: [Dabke, handConnection, dancers hold hands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handConnection Context triple: [Dabke, handConnection, dancers hold hands]
-
A.
handPosition
Indicates the spatial location or orientation of a hand relative to a reference point or object.
-
B.
handCondition
Indicates the state or quality of a hand, such as its health, functionality, or any specific condition affecting it.
-
C.
keyHandInvolves
Indicates that a key hand action or event involves a particular participant, object, or entity as part of that interaction.
-
D.
handsOverTo
Indicates that one entity transfers possession, control, or responsibility of something directly to another entity.
-
E.
usesHandGestures
Indicates that an entity communicates or expresses itself by making deliberate movements or signals with its hands.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b034bc74819091250f91ba5174c0 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:49 p.m.