Triple
T26308391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosemont College |
E661750
|
entity |
| Predicate | currentGenderAdmissionPolicy |
P16158
|
FINISHED |
| Object | coeducational |
—
|
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: coeducational | Statement: [Rosemont College, currentGenderAdmissionPolicy, coeducational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentGenderAdmissionPolicy Context triple: [Rosemont College, currentGenderAdmissionPolicy, coeducational]
-
A.
admissionGender
chosen
Indicates the gender-based criteria or classification applied in the context of admission or entry decisions.
-
B.
formerGenderAdmission
Indicates that an institution previously admitted a particular gender but no longer does so.
-
C.
hasGenderPolicy
Indicates that an entity has adopted, implemented, or is governed by a specific policy related to gender issues or gender equality.
-
D.
hasGenderRequirement
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
E.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 26, 2026, 10:20 p.m.