Triple
T1917879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rawdah ash-Sharifah |
E40058
|
entity |
| Predicate | genderAccess |
P25470
|
FINISHED |
| Object | separate times for men and women |
—
|
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: separate times for men and women | Statement: [Rawdah ash-Sharifah, genderAccess, separate times for men and women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderAccess Context triple: [Rawdah ash-Sharifah, genderAccess, separate times for men and women]
-
A.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
B.
genderUsage
Indicates how a particular gender is applied, referenced, or treated within a given context or system.
-
C.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
D.
genderDivision
chosen
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
E.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2107fe48190bafff825f1f805ad |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.