Triple
T26002189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament (Qualification of Women) Act 1918 |
E646658
|
entity |
| Predicate | genderCriterionForMPs |
P80115
|
FINISHED |
| Object | removed |
—
|
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: removed | Statement: [Parliament (Qualification of Women) Act 1918, genderCriterionForMPs, removed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderCriterionForMPs Context triple: [Parliament (Qualification of Women) Act 1918, genderCriterionForMPs, removed]
-
A.
officeHoldersGenderEligibility
chosen
Indicates the gender-based criteria that determine who is eligible to hold a particular office or position.
-
B.
incumbentGender
Indicates the gender of the person currently holding a particular position or office.
-
C.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
D.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
E.
hasGenderOfPerson
Indicates that a person is associated with a specific gender classification.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605770b2481908c1674952889f62f |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9 a.m.