Triple
T4257659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saybrook College |
E96017
|
entity |
| Predicate | studentPopulationType |
P5947
|
FINISHED |
| Object | Yale undergraduates |
—
|
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: Yale undergraduates | Statement: [Saybrook College, studentPopulationType, Yale undergraduates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentPopulationType Context triple: [Saybrook College, studentPopulationType, Yale undergraduates]
-
A.
studentPopulationLevel
Indicates the relative size or magnitude of the student population associated with an entity.
-
B.
servesStudentPopulation
Indicates that an entity provides services, resources, or support to a defined group of students.
-
C.
hasPopulationType
chosen
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
D.
studentBodySize
Indicates the total number of students that make up the student body of an institution or group.
-
E.
hadPopulationType
Indicates that an entity possessed a particular classification or type of population during a given time or 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ec321008190b2cc1aca6ab690c4 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.