Triple
T25419101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geo T. Wilkins Junior High School |
E636927
|
entity |
| Predicate | studentAgeGroup |
P19123
|
FINISHED |
| Object | early adolescents |
—
|
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: early adolescents | Statement: [Geo T. Wilkins Junior High School, studentAgeGroup, early adolescents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentAgeGroup Context triple: [Geo T. Wilkins Junior High School, studentAgeGroup, early adolescents]
-
A.
ageGroup
chosen
Indicates the categorical age range or bracket to which an entity belongs.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageGroupInvolved
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
-
D.
ageGroupIndicated
Indicates that a specific age range or category is identified or assigned to an entity.
-
E.
inUniverseAgeGroup
Indicates that an entity belongs to a specified age group within a particular fictional or defined universe or setting.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:55 p.m.