Triple
T141169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winn Brook School |
E2852
|
entity |
| Predicate | schoolLevel |
P177
|
FINISHED |
| Object | elementary |
—
|
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: elementary | Statement: [Winn Brook School, schoolLevel, elementary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolLevel Context triple: [Winn Brook School, schoolLevel, elementary]
-
A.
educationType
chosen
Indicates the specific category or level of education associated with an entity, such as formal, informal, primary, secondary, or higher education.
-
B.
orderGradeLevel
Indicates the relative sequencing or ranking of grade levels, specifying which grade comes before or after another.
-
C.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
-
D.
schoolBoard
Indicates that an entity serves as or is governed by a school board responsible for overseeing educational policies and administration.
-
E.
servesGradeLevels
Indicates that an entity (such as a school or program) provides services or instruction to students in the specified grade levels.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.