Triple
T28134306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Perse Upper |
E714156
|
entity |
| Predicate | isSeniorSectionOf |
P52338
|
FINISHED |
| Object | The Perse School |
—
|
NE NERFINISHED |
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: The Perse School | Statement: [The Perse Upper, isSeniorSectionOf, The Perse School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeniorSectionOf Context triple: [The Perse Upper, isSeniorSectionOf, The Perse School]
-
A.
hasSeniorSection
chosen
Indicates that an entity includes or is associated with a designated section or area specifically intended for seniors.
-
B.
isSeniorOfficialFor
Indicates that one entity holds a high-ranking or senior official position within, or on behalf of, another entity.
-
C.
hasJuniorSection
Indicates that an entity includes or is associated with a subordinate or lower-level section within its structure or organization.
-
D.
isSeniorTo
Indicates that one entity holds a higher rank, status, or level of authority than another.
-
E.
isSeniorBodyWithin
Indicates that one body or organizational unit is hierarchically contained within, and subordinate to, a higher-level senior body.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6412d52188190b88347a75851b840 |
completed | May 2, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:48 p.m.