Triple
T27808082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Misunderstanding of Teyana Taylor |
E702444
|
entity |
| Predicate | mainPerformerSexOrGender |
P20803
|
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: [The Misunderstanding of Teyana Taylor, mainPerformerSexOrGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerSexOrGender Context triple: [The Misunderstanding of Teyana Taylor, mainPerformerSexOrGender, female]
-
A.
hasPerformerGender
chosen
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
creatorSexOrGender
Indicates that the specified sex or gender is the sex or gender of the creator of the referenced work or entity.
-
C.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
D.
sexType
Indicates the specific category or type of sexual activity or sexual relationship involved between entities.
-
E.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 5:40 p.m.