Triple
T24177484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cypriot folk dance |
E599320
|
entity |
| Predicate | genderPattern |
P51833
|
FINISHED |
| Object | mixed-gender participation |
—
|
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: mixed-gender participation | Statement: [Cypriot folk dance, genderPattern, mixed-gender participation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderPattern Context triple: [Cypriot folk dance, genderPattern, mixed-gender participation]
-
A.
genderUsage
Indicates how a particular gender is applied, referenced, or treated within a given context or system.
-
B.
genderConfiguration
chosen
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
C.
genderSpecificity
Indicates whether the relationship or action applies specifically to a particular gender or is gender-neutral.
-
D.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
-
E.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.