Triple
T31731680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclones |
E809876
|
entity |
| Predicate | homeInstitutionGenderHistory |
P51355
|
FINISHED |
| Object | historically 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: historically women’s college | Statement: [Cyclones, homeInstitutionGenderHistory, historically women’s college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeInstitutionGenderHistory Context triple: [Cyclones, homeInstitutionGenderHistory, historically women’s college]
-
A.
hasGenderHistory
chosen
Indicates that an entity has undergone or experienced a change or transition in gender over time.
-
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.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
D.
historicallyAttracted
Indicates that one entity has experienced attraction toward another at some point in the past.
-
E.
homeInstitutionLocation
Indicates the geographic place where an entity’s primary or home institution is located.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab1f713481908b13cd1055894e37 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:21 p.m.