Triple
T4636251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheam School |
E101538
|
entity |
| Predicate | hasPrePrepDepartment |
P57877
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cheam School, hasPrePrepDepartment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrePrepDepartment Context triple: [Cheam School, hasPrePrepDepartment, yes]
-
A.
offeredByDepartment
Indicates that something, such as a course or program, is provided or made available by a specific department.
-
B.
hasSupportingOffice
Indicates that an entity is associated with or served by a particular office that provides support or administrative services to it.
-
C.
hasSecondaryHall
Indicates that an entity is associated with or contains an additional, subordinate hall beyond its primary hall.
-
D.
hasAcademicDepartment
Indicates that an institution or organization includes or is associated with a specific academic department.
-
E.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a60a66c8190b76f3d3a7da1df55 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56f7b94481909f3335312becd446 |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:13 p.m.