Triple
T19884539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encina Preparatory High School |
E477861
|
entity |
| Predicate | hasTargetStudentAgeRange |
P133314
|
FINISHED |
| Object | teenagers |
—
|
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: teenagers | Statement: [Encina Preparatory High School, hasTargetStudentAgeRange, teenagers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetStudentAgeRange Context triple: [Encina Preparatory High School, hasTargetStudentAgeRange, teenagers]
-
A.
hasTargetStudentProfile
chosen
Indicates that an entity is associated with or intended for a specific type of student characterized by a defined profile.
-
B.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
C.
supportsAgeRange
Indicates that one entity is compatible with, valid for, or designed to accommodate a specified range of ages.
-
D.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
E.
hasDegreeRange
Indicates that an entity is associated with a minimum and maximum degree value defining a range.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659093df081909d3be9c3caeb79ba |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.