Triple
T225952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morehouse College |
E4313
|
entity |
| Predicate | genderAdmissionPolicy |
P277
|
FINISHED |
| Object | men only undergraduate program |
—
|
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 undergraduate program | Statement: [Morehouse College, genderAdmissionPolicy, men only undergraduate program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderAdmissionPolicy Context triple: [Morehouse College, genderAdmissionPolicy, men only undergraduate program]
-
A.
hasGenderPolicy
chosen
Indicates that an entity has adopted, implemented, or is governed by a specific policy related to gender issues or gender equality.
-
B.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
C.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
D.
admissionPolicy
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
E.
hasNumberOfGenders
Indicates the relationship that specifies how many distinct genders are associated with or recognized for a given 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.