Triple
T28863340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham University Queen’s Campus |
E728923
|
entity |
| Predicate | studentPopulationPeakApprox |
P101078
|
FINISHED |
| Object | 2000–3000 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: 2000–3000 students | Statement: [Durham University Queen’s Campus, studentPopulationPeakApprox, 2000–3000 students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentPopulationPeakApprox Context triple: [Durham University Queen’s Campus, studentPopulationPeakApprox, 2000–3000 students]
-
A.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
B.
studentPopulationLevel
Indicates the relative size or magnitude of the student population associated with an entity.
-
C.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
D.
peakPopulationApproximate
chosen
Indicates that the peak population of an entity is known only approximately rather than as an exact value.
-
E.
numberOfEmployeesAtPeak
Indicates the highest recorded count of employees that an entity had at any point in time.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a18f3d4819097fe33426c585827 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:48 a.m.