Triple
T399708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Technology, University of Cambridge |
E9251
|
entity |
| Predicate | studentBodyIncludes |
P5246
|
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: [School of Technology, University of Cambridge, studentBodyIncludes, undergraduate students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentBodyIncludes Context triple: [School of Technology, University of Cambridge, studentBodyIncludes, undergraduate students]
-
A.
studentBodySize
Indicates the total number of students that make up the student body of an institution or group.
-
B.
hasStudentBodyType
chosen
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
C.
studentBodyFocus
Indicates that the primary attention, concern, or efforts are directed toward the student body as a whole.
-
D.
studentSection
Indicates a relationship where a student is enrolled in or associated with a particular course section.
-
E.
studentsWing
Indicates a relationship where a particular wing, section, or area is designated for or associated with students.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8d0ca881909d786e8eed9b6748 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.