Triple
T33354115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Fairfield Middle School |
E854023
|
entity |
| Predicate | hasSchoolLunchProgram |
P191994
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [New Fairfield Middle School, hasSchoolLunchProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchoolLunchProgram Context triple: [New Fairfield Middle School, hasSchoolLunchProgram, yes]
-
A.
hasFeederSchool
Indicates that one educational institution regularly supplies or channels its graduating students into another institution as part of an established progression pathway.
-
B.
hasSchoolsAccess
Indicates that one entity has permission or the ability to access schools or school-related resources associated with another entity.
-
C.
schoolProgram
Indicates that an entity is an educational program offered or administered by a particular school or educational institution.
-
D.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
-
E.
hasSchoolOrganization
Indicates that an educational institution is associated with or contains a specific school-related organization or group.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 1, 2026, 1:34 a.m.