Triple
T10049407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come As You Are |
E207706
|
entity |
| Predicate | hasPrimaryPerformerGender |
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: [Come As You Are, hasPrimaryPerformerGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPerformerGender Context triple: [Come As You Are, hasPrimaryPerformerGender, female]
-
A.
hasPerformerGender
chosen
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
hasPerformerGenderComposition
Indicates the gender makeup of the group of performers involved in an event or performance.
-
C.
hasLeadCharacterGender
Indicates that the primary or lead character in a work has a specified gender.
-
D.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf8e41c4819091fa12742197e207 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.