Triple
T29132536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle Haleine: Eau de Voilette |
E738417
|
entity |
| Predicate | creatorGenderPlay |
P73491
|
FINISHED |
| Object | use of female pseudonym |
—
|
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: use of female pseudonym | Statement: [Belle Haleine: Eau de Voilette, creatorGenderPlay, use of female pseudonym]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorGenderPlay Context triple: [Belle Haleine: Eau de Voilette, creatorGenderPlay, use of female pseudonym]
-
A.
creatorSexOrGender
Indicates that the specified sex or gender is the sex or gender of the creator of the referenced work or entity.
-
B.
playsGender
chosen
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
-
C.
playableGender
Indicates that a particular gender is available as a selectable option for a player character.
-
D.
featuredGender
Indicates that a particular gender is highlighted, emphasized, or given primary focus in a given context or presentation.
-
E.
genderOfPersona
Indicates the gender identity associated with a given persona.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 11:32 a.m.