Triple
T34363479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Body and Soul |
E881943
|
entity |
| Predicate | hasPerformerGenderIdentity |
P43613
|
FINISHED |
| Object | transgender woman |
—
|
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: transgender woman | Statement: [Body and Soul, hasPerformerGenderIdentity, transgender woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerGenderIdentity Context triple: [Body and Soul, hasPerformerGenderIdentity, transgender woman]
-
A.
hasPerformerGender
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
hasGenderIdentity
chosen
Indicates that an entity identifies with or experiences a particular gender.
-
C.
hasPerformerGenderComposition
Indicates the gender makeup of the group of performers involved in an event or performance.
-
D.
publiclyIdentifiesAs
Indicates that an entity openly declares or presents themself to others as having a particular identity or role.
-
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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 1:58 a.m.