Triple
T25489440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagavata Mela Natakam |
E638798
|
entity |
| Predicate | hasTraditionalGenderRule |
P133302
|
FINISHED |
| Object | all-male cast |
—
|
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: all-male cast | Statement: [Bhagavata Mela Natakam, hasTraditionalGenderRule, all-male cast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalGenderRule Context triple: [Bhagavata Mela Natakam, hasTraditionalGenderRule, all-male cast]
-
A.
hasGenderConvention
chosen
Indicates that there is an established or customary way of assigning or expressing gender within a given context, system, or culture.
-
B.
hasGenderInSomeTraditions
Indicates that, in at least some cultural, religious, or historical traditions, the subject is regarded as having a specific gender.
-
C.
hasGenderFormat
Indicates that something is associated with or expressed in a particular gender-related format or representation.
-
D.
hasGenderSystem
Indicates that an entity employs or is characterized by a particular system for categorizing gender.
-
E.
hasAlternativeGenderUsage
Indicates that an entity is used with a different or non-standard gender form in certain contexts or usages.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 2:34 p.m.