Triple
T37521804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edial Hall School |
E932797
|
entity |
| Predicate | numberOfPupilsAtPeak |
P205951
|
FINISHED |
| Object | about eight |
—
|
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: about eight | Statement: [Edial Hall School, numberOfPupilsAtPeak, about eight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPupilsAtPeak Context triple: [Edial Hall School, numberOfPupilsAtPeak, about eight]
-
A.
numberOfEmployeesAtPeak
Indicates the highest recorded count of employees that an entity had at any point in time.
-
B.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
C.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
D.
numberOfInstitutesAtPeak
Indicates the total count of institutes an entity had at the highest point in its history or development.
-
E.
hasNumberOfSeatsAtPeak
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
- F. None of above. chosen
Provenance (4 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.