Triple
T7105918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale World Fellows Program |
E165582
|
entity |
| Predicate | cohortSize |
P53768
|
FINISHED |
| Object | approximately 16 to 18 fellows per year |
—
|
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: approximately 16 to 18 fellows per year | Statement: [Yale World Fellows Program, cohortSize, approximately 16 to 18 fellows per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cohortSize Context triple: [Yale World Fellows Program, cohortSize, approximately 16 to 18 fellows per year]
-
A.
hasTypicalFirstCohortSize
Indicates the usual or standard number of individuals in the first cohort associated with an entity.
-
B.
enrollmentSize
chosen
Indicates the number of individuals enrolled or registered in a particular group, program, or institution.
-
C.
collaborationSize
Indicates the number of participants involved together in a given collaborative relationship or activity.
-
D.
colonySize
Indicates the number of individuals or units that make up a colony in the described context.
-
E.
sampleSize
Indicates the number of units, observations, or instances included in a particular study, experiment, or dataset.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b892008190827fa1e5eab2e558 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.