Triple
T26436597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacMurray College |
E664965
|
entity |
| Predicate | formerGenderStatus |
P14517
|
FINISHED |
| Object | women's college |
—
|
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: women's college | Statement: [MacMurray College, formerGenderStatus, women's college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerGenderStatus Context triple: [MacMurray College, formerGenderStatus, women's college]
-
A.
formerGenderAdmission
chosen
Indicates that an institution previously admitted a particular gender but no longer does so.
-
B.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
C.
sexStatus
Indicates whether and how a sexual relationship or sexual activity exists or has occurred between the related entities.
-
D.
genderVariant
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or gender.
-
E.
genderCustom
Indicates that an entity has a user-specified or non-standard gender designation beyond predefined gender categories.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 26, 2026, 11:54 p.m.