Triple
T7353139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covert Elementary School |
E169553
|
entity |
| Predicate | servesStudentAgeRange |
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: [Covert Elementary School, servesStudentAgeRange, young students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStudentAgeRange Context triple: [Covert Elementary School, servesStudentAgeRange, young students]
-
A.
servesAgeRange
chosen
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
B.
servesGradeLevels
Indicates that an entity (such as a school or program) provides services or instruction to students in the specified grade levels.
-
C.
acceptsPupilsFromAge
Indicates that an entity (such as a school or program) enrolls or admits pupils starting from a specified minimum age.
-
D.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
typicalAgeAtCompletion
Indicates the age at which an entity (such as a program, activity, or process) is typically completed.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.