Triple
T34282397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebron, Connecticut |
E879626
|
entity |
| Predicate | highSchoolForStudents |
P89172
|
FINISHED |
| Object | RHAM High 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: RHAM High School | Statement: [Hebron, Connecticut, highSchoolForStudents, RHAM High School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highSchoolForStudents Context triple: [Hebron, Connecticut, highSchoolForStudents, RHAM High School]
-
A.
highSchoolForMostStudents
Indicates that the referenced school is the primary high school attended by the majority of students in a given group or area.
-
B.
highSchoolSetting
Indicates that an event, interaction, or situation takes place within the context or environment of a high school.
-
C.
subjectHighSchool
chosen
Indicates that the subject attended or was enrolled in the referenced high school.
-
D.
servesHighSchool
Indicates that an entity provides services, support, or resources specifically to a high school.
-
E.
highSchoolStatus
Indicates the relationship between a person and their current or completed status in high school (e.g., enrolled, graduated, dropped out).
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.