Triple
T26389146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orangeville Prep |
E663363
|
entity |
| Predicate | targetAthleteAgeGroup |
P133912
|
FINISHED |
| Object | high school age athletes |
—
|
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: high school age athletes | Statement: [Orangeville Prep, targetAthleteAgeGroup, high school age athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAthleteAgeGroup Context triple: [Orangeville Prep, targetAthleteAgeGroup, high school age athletes]
-
A.
typeOfAthlete
Indicates that one entity is an athlete and the other specifies the kind or category of athlete they are.
-
B.
typicalAgeRangeOfPlayers
chosen
Indicates the usual age range of people who typically play or participate in something.
-
C.
raceTypeByAge
Indicates that the type or category of a race is determined or classified based on the ages of its participants.
-
D.
performedForAgeGroup
Indicates that an action or performance is specifically intended for, targeted at, or carried out on behalf of a particular age group.
-
E.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 26, 2026, 11:24 p.m.