Triple
T3939373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneers |
E91994
|
entity |
| Predicate | homeInstitutionGender |
P16158
|
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: [Pioneers, homeInstitutionGender, women's college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeInstitutionGender Context triple: [Pioneers, homeInstitutionGender, women's college]
-
A.
hostsInstitution
Indicates that one entity serves as the hosting location or organizing body for an institution.
-
B.
homeInstitutionFoundedIn
Indicates that the institution serving as a home or primary affiliation for an entity was established in a specified year or time period.
-
C.
admissionGender
chosen
Indicates the gender-based criteria or classification applied in the context of admission or entry decisions.
-
D.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
-
E.
hadInstitution
Indicates that an entity was affiliated with, operated within, or was served by a particular institution during some period of time.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfb12b88190a6ca6574b1aadb6e |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.