Triple
T2837668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Births |
E62388
|
entity |
| Predicate | promotedRoleOfWomen |
P42182
|
FINISHED |
| Object | mothers of many children |
—
|
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: mothers of many children | Statement: [Battle for Births, promotedRoleOfWomen, mothers of many children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedRoleOfWomen Context triple: [Battle for Births, promotedRoleOfWomen, mothers of many children]
-
A.
genderEquality
Indicates that the relationship or action promotes, reflects, or ensures equal rights, opportunities, and treatment for all genders without discrimination.
-
B.
womenStatus
chosen
Indicates the social, legal, economic, or cultural position or condition assigned to women within a given context or system.
-
C.
hadWomenOrganization
Indicates that an entity was associated with or involved in an organization focused on women or women’s issues.
-
D.
admittedWomen
Indicates that an entity allowed or accepted women into a place, group, institution, or event.
-
E.
stanceOnWomenInMinistry
Indicates a subject’s position or viewpoint regarding the role and participation of women in ministry or religious leadership.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdeede0488190a9782f55b57559ee |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.