Triple
T32094189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christchurch Boys' High School |
E819681
|
entity |
| Predicate | hasAlumniGroup |
P51
|
FINISHED |
| Object | Old Boys |
—
|
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: Old Boys | Statement: [Christchurch Boys' High School, hasAlumniGroup, Old Boys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlumniGroup Context triple: [Christchurch Boys' High School, hasAlumniGroup, Old Boys]
-
A.
hasAlumni
chosen
Indicates that an institution or organization is associated with individuals who formerly attended or graduated from it.
-
B.
hasAlumniNetwork
Indicates that an entity maintains or is associated with an organized network or community of its former members or graduates.
-
C.
hasAlumnusTeam
Indicates a relationship where an educational institution is associated with a sports team composed of its former students (alumni).
-
D.
hasAlumniField
Indicates a relationship where an entity is associated with a specific field or area of study in which its alumni specialized or graduated.
-
E.
hasAlumniInvolvement
Indicates that an entity maintains an ongoing relationship or engagement with its former members or graduates.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 12:25 a.m.