Triple
T28570613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXX's and OOO's (An American Girl) |
E722804
|
entity |
| Predicate | hasPerformerGenderFocus |
P2452
|
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: [XXX's and OOO's (An American Girl), hasPerformerGenderFocus, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerGenderFocus Context triple: [XXX's and OOO's (An American Girl), hasPerformerGenderFocus, female]
-
A.
hasPerformerGender
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
hasGenderFocus
chosen
Indicates that something is specifically concerned with, oriented toward, or primarily addressing a particular gender or gender-related issues.
-
C.
hasPerformerGenderComposition
Indicates the gender makeup of the group of performers involved in an event or performance.
-
D.
genderCategoryIncludes
Indicates that a given gender category encompasses or contains the specified gender identity or subgroup.
-
E.
hasLeadCharacterGender
Indicates that the primary or lead character in a work has a specified gender.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 4:09 a.m.