Triple
T10325530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Place of Many Mothers |
E242751
|
entity |
| Predicate | genderDominance |
P93381
|
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: [Green Place of Many Mothers, genderDominance, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderDominance Context triple: [Green Place of Many Mothers, genderDominance, female]
-
A.
domesticDominance
Indicates a relationship where one entity holds primary control, influence, or superiority over another within a domestic or home-based context.
-
B.
sexualRole
Indicates the specific sexual function, position, or behavioral role one entity assumes in a sexual interaction or relationship with another.
-
C.
genderNorms
Indicates socially constructed expectations or rules about how individuals should behave, appear, or identify based on their perceived gender.
-
D.
genderImplication
Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
-
E.
genderTarget
Indicates that an action, message, or effect is specifically directed toward entities of a particular gender.
- F. None of above. chosen
Provenance (4 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cd76348190b93562112300acfc |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:51 a.m.