Triple
T21026122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betty Parsons Gallery |
E517945
|
entity |
| Predicate | representedGender |
P95608
|
FINISHED |
| Object | women artists |
—
|
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: women artists | Statement: [Betty Parsons Gallery, representedGender, women artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedGender Context triple: [Betty Parsons Gallery, representedGender, women artists]
-
A.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
B.
genderCustom
Indicates that an entity has a user-specified or non-standard gender designation beyond predefined gender categories.
-
C.
genderDepicted
chosen
Indicates that the relationship specifies the gender of the entity as it is represented or portrayed in some context.
-
D.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
E.
genderVariant
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7c262c8190bceb8fd26be76983 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.