Triple
T7829033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbor Day School |
E181318
|
entity |
| Predicate | studentAgeRangeFrom |
P78715
|
FINISHED |
| Object | approximately 5 years |
—
|
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: approximately 5 years | Statement: [Harbor Day School, studentAgeRangeFrom, approximately 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentAgeRangeFrom Context triple: [Harbor Day School, studentAgeRangeFrom, approximately 5 years]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
acceptsPupilsFromAge
Indicates that an entity (such as a school or program) enrolls or admits pupils starting from a specified minimum age.
-
C.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
-
D.
typicalAgeRangeLower
chosen
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
E.
primaryStudentAgeRange
Indicates the typical or required age range associated with primary-level students in a given context.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04aaed1881908e1da129a43ef9c7 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.