Triple
T2223625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simmons University |
E48596
|
entity |
| Predicate | undergraduateAdmissionPolicy |
P17959
|
FINISHED |
| Object | primarily women |
—
|
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: primarily women | Statement: [Simmons University, undergraduateAdmissionPolicy, primarily women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergraduateAdmissionPolicy Context triple: [Simmons University, undergraduateAdmissionPolicy, primarily women]
-
A.
postgraduateIntakePolicy
Indicates the rules or criteria governing how an institution admits or selects postgraduate students.
-
B.
undergraduateIntakeType
chosen
Indicates the specific category or mode by which undergraduate students are admitted or enrolled into an academic program or institution.
-
C.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
D.
undergraduateEnrollment
Indicates the number of undergraduate students enrolled in an institution or program.
-
E.
admissionsLevel
Indicates the degree or category of access, entry, or acceptance granted in an admissions context.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03d1df88190950c691a4c246bd1 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.