Triple
T27347713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic feminism |
E684272
|
entity |
| Predicate | seeksReformOf |
P72107
|
FINISHED |
| Object | custody laws |
—
|
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: custody laws | Statement: [Islamic feminism, seeksReformOf, custody laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksReformOf Context triple: [Islamic feminism, seeksReformOf, custody laws]
-
A.
seeksToReform
chosen
Indicates an entity’s intention or effort to change an existing system, practice, or condition in order to improve or correct it.
-
B.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
C.
isPartOfReform
Indicates that an action, measure, or component belongs to, contributes to, or is included within a broader reform initiative or process.
-
D.
advocatedReformOf
Indicates that one entity publicly supported or promoted changes to another entity, typically aiming to improve or modify its structure, policies, or practices.
-
E.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:46 a.m.