Triple
T4717899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braintree High School |
E104692
|
entity |
| Predicate | hasSchoolHours |
P59140
|
FINISHED |
| Object | day school |
—
|
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: day school | Statement: [Braintree High School, hasSchoolHours, day school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchoolHours Context triple: [Braintree High School, hasSchoolHours, day school]
-
A.
hasSchool
Indicates that an entity possesses, is associated with, or is served by a particular school.
-
B.
hasSchoolsAccess
Indicates that one entity has permission or the ability to access schools or school-related resources associated with another entity.
-
C.
hasDayStudents
Indicates that an educational institution has students who attend during the day but do not reside on campus.
-
D.
hasSchoolYears
Indicates a relationship where an educational institution is associated with specific academic years or grade levels it offers or covers.
-
E.
hasSchoolCategory
Indicates that an entity (such as a school or educational institution) is associated with a particular category or type of school.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:18 p.m.