Triple
T8855945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Åbo Akademi University |
E210756
|
entity |
| Predicate | studentPopulationApprox |
P30984
|
FINISHED |
| Object | 5000–6000 |
—
|
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: 5000–6000 | Statement: [Åbo Akademi University, studentPopulationApprox, 5000–6000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentPopulationApprox Context triple: [Åbo Akademi University, studentPopulationApprox, 5000–6000]
-
A.
studentPopulationLevel
Indicates the relative size or magnitude of the student population associated with an entity.
-
B.
servesStudentPopulation
Indicates that an entity provides services, resources, or support to a defined group of students.
-
C.
hasApproximateStudents
chosen
Indicates that an entity is associated with an estimated or approximate number of students, rather than an exact count.
-
D.
primaryStudentPopulation
Indicates the number or group of students who are enrolled at the primary or elementary level within an educational institution or system.
-
E.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c7f51881909c847989f31f203a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.