Triple
T7164419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohiniyattam |
E167030
|
entity |
| Predicate | primaryGenderTradition |
P34349
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Mohiniyattam, primaryGenderTradition, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGenderTradition Context triple: [Mohiniyattam, primaryGenderTradition, female]
-
A.
hasGenderInSomeTraditions
Indicates that, in at least some cultural, religious, or historical traditions, the subject is regarded as having a specific gender.
-
B.
genderNorms
Indicates socially constructed expectations or rules about how individuals should behave, appear, or identify based on their perceived gender.
-
C.
hasTypicalGenderAssociation
chosen
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
D.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
E.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e83168a08190937ff46797d94f3e |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.