Triple
T30683094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrtos |
E781108
|
entity |
| Predicate | isSocialDance |
P170029
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Syrtos, isSocialDance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSocialDance Context triple: [Syrtos, isSocialDance, yes]
-
A.
isPartnerDance
Indicates that the relationship between the entities is that they participate together in a partnered dance.
-
B.
danceSuitability
Indicates how appropriate or well-suited something (such as music, a space, or attire) is for dancing.
-
C.
usedInDance
Indicates that something is employed or incorporated as a component or element within a dance performance or practice.
-
D.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
E.
isLeadFollowDance
Indicates that two entities are engaged in a partnered dance where one takes the lead role and the other follows.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b81f12c8190a0aaacc0a54f9db5 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:33 p.m.