Triple
T5449739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Bergen |
E122338
|
entity |
| Predicate | hasStudentBodySize |
P3395
|
FINISHED |
| Object | over 17,000 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: over 17,000 students | Statement: [University of Bergen, hasStudentBodySize, over 17,000 students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentBodySize Context triple: [University of Bergen, hasStudentBodySize, over 17,000 students]
-
A.
studentBodySize
chosen
Indicates the total number of students that make up the student body of an institution or group.
-
B.
hasStudentBodyType
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
C.
hasStudentBodyFrom
Indicates that an educational institution draws or enrolls its student body from a specified geographic area, group, or source.
-
D.
typicalClassSize
Indicates the usual or average number of students (or participants) that are present in a single class or course section.
-
E.
campusSize
Indicates the physical extent or scale of a campus, typically measured in area or capacity.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.