Triple
T20534069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Leech Elementary School |
E504146
|
entity |
| Predicate | servesStudentAgeGroup |
P3005
|
FINISHED |
| Object | young students |
—
|
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: young students | Statement: [David Leech Elementary School, servesStudentAgeGroup, young students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStudentAgeGroup Context triple: [David Leech Elementary School, servesStudentAgeGroup, young students]
-
A.
servesGradeLevels
Indicates that an entity (such as a school or program) provides services or instruction to students in the specified grade levels.
-
B.
servesAgeRange
chosen
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
C.
usesStudentsFor
Indicates that one entity employs or exploits students as a resource or means to carry out its activities or achieve its objectives.
-
D.
servesHighSchool
Indicates that an entity provides services, support, or resources specifically to a high school.
-
E.
targetStudentGroup
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06d30508190a13d1a9855b441fb |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.