Triple
T32924423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal House of Justice |
E842228
|
entity |
| Predicate | membershipGenderPolicy |
P15554
|
FINISHED |
| Object | men only |
—
|
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: men only | Statement: [Universal House of Justice, membershipGenderPolicy, men only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipGenderPolicy Context triple: [Universal House of Justice, membershipGenderPolicy, men only]
-
A.
hasGenderPolicy
Indicates that an entity has adopted, implemented, or is governed by a specific policy related to gender issues or gender equality.
-
B.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
C.
hasGenderNeutralEligibility
Indicates that an entity is eligible or applicable in a way that does not depend on or specify a particular gender.
-
D.
membershipCondition
Indicates the rule, requirement, or criterion that determines whether an entity qualifies for membership in a given group or set.
-
E.
genderOfMembers
Indicates the gender or genders associated with the members of a group or organization.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:20 a.m.