Triple
T1587974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon University System |
E34108
|
entity |
| Predicate | studentsServed |
P9355
|
FINISHED |
| Object | tens of thousands of students 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: tens of thousands of students per year | Statement: [Oregon University System, studentsServed, tens of thousands of students per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentsServed Context triple: [Oregon University System, studentsServed, tens of thousands of students per year]
-
A.
servesStudentPopulation
chosen
Indicates that an entity provides services, resources, or support to a defined group of students.
-
B.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
C.
studentPopulationLevel
Indicates the relative size or magnitude of the student population associated with an entity.
-
D.
studentsWing
Indicates a relationship where a particular wing, section, or area is designated for or associated with students.
-
E.
hasDayStudents
Indicates that an educational institution has students who attend during the day but do not reside on campus.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.