Triple
T2666359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapin School |
E55644
|
entity |
| Predicate | studentGenderRestriction |
P32136
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Chapin School, studentGenderRestriction, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentGenderRestriction Context triple: [Chapin School, studentGenderRestriction, female]
-
A.
hasGenderRequirement
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
B.
admissionGender
Indicates the gender-based criteria or classification applied in the context of admission or entry decisions.
-
C.
hasGenderPolicy
Indicates that an entity has adopted, implemented, or is governed by a specific policy related to gender issues or gender equality.
-
D.
isSingleSex
chosen
Indicates that the entity involves or is restricted to only one biological sex or gender, rather than being mixed or coeducational.
-
E.
hasGenderSystem
Indicates that an entity employs or is characterized by a particular system for categorizing gender.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd97040e48190b0a87489f108810e |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.