Triple
T24658015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thornton Academy |
E610447
|
entity |
| Predicate | offersBoardingForGrades |
P157164
|
FINISHED |
| Object | 9–12 |
—
|
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: 9–12 | Statement: [Thornton Academy, offersBoardingForGrades, 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersBoardingForGrades Context triple: [Thornton Academy, offersBoardingForGrades, 9–12]
-
A.
offersGrades
Indicates that one entity provides or assigns academic grades to another entity.
-
B.
servesGradeLevels
Indicates that an entity (such as a school or program) provides services or instruction to students in the specified grade levels.
-
C.
eligibleGradeLevels
Indicates the grade levels for which something (such as a program, course, or benefit) is considered eligible or applicable.
-
D.
hasGradeListing
Indicates that an entity is associated with a specific grade entry or record in a grading or classification system.
-
E.
onBoardClass
Indicates that one entity is a class or category of service available on board another entity (such as a vehicle, vessel, or aircraft).
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 2:34 a.m.