Triple
T403956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloucester Cathedral choir school |
E9343
|
entity |
| Predicate | hasPupilType |
P5246
|
FINISHED |
| Object | boy choristers |
—
|
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: boy choristers | Statement: [Gloucester Cathedral choir school, hasPupilType, boy choristers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPupilType Context triple: [Gloucester Cathedral choir school, hasPupilType, boy choristers]
-
A.
hasStudentBodyType
chosen
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
B.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
C.
isStudiedIn
Indicates that a subject (such as a topic, field, or phenomenon) is examined, researched, or learned about within a particular context, environment, or discipline.
-
D.
notablePupil
Indicates that one person is a distinguished or noteworthy student or protégé of another person.
-
E.
hasFacultyType
Indicates that a faculty member or academic unit is associated with a specific category or type of faculty (e.g., full-time, adjunct, visiting).
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca226fc81909d6ccc38a637daa6 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.