Triple
T424240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Quakers track and field |
E8169
|
entity |
| Predicate | hasStudentAthletes |
P3611
|
FINISHED |
| Object | undergraduate students |
—
|
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: undergraduate students | Statement: [Penn Quakers track and field, hasStudentAthletes, undergraduate students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentAthletes Context triple: [Penn Quakers track and field, hasStudentAthletes, undergraduate students]
-
A.
hasNumberOfStudentAthletes
Indicates the relationship that specifies how many student athletes are associated with a given entity.
-
B.
studentAthletes
chosen
Indicates a relationship where the entities are athletes who are also enrolled as students, combining academic and athletic roles.
-
C.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
D.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
E.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational institution.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed3e4cc8190ba6aff3bd1adb06f |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd5439c8190aea661b8b4aa51e9 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.