Triple
T14995298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F. N. Brown School |
E373942
|
entity |
| Predicate | servesStudents |
P9355
|
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: [F. N. Brown School, servesStudents, young students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStudents Context triple: [F. N. Brown School, servesStudents, young students]
-
A.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
B.
hasStudentServices
Indicates that an entity provides or is associated with student support services for another entity or group.
-
C.
servesStudentPopulation
chosen
Indicates that an entity provides services, resources, or support to a defined group of students.
-
D.
targetStudentService
Indicates a relationship where a particular student is the intended recipient or focus of a specific service or support action.
-
E.
studentsReceive
Indicates that one or more students are the recipients of something, such as instruction, resources, or communications, from another source.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.