Triple
T854460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. George's School |
E18458
|
entity |
| Predicate | hasAthleticsProgram |
P54
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [St. George's School, hasAthleticsProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAthleticsProgram Context triple: [St. George's School, hasAthleticsProgram, yes]
-
A.
hasAthletics
chosen
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
B.
parentAthleticProgram
Indicates that one athletic program serves as the overarching or higher-level program to which another athletic program belongs or is subordinate.
-
C.
hasNumberOfStudentAthletes
Indicates the relationship that specifies how many student athletes are associated with a given entity.
-
D.
hasStrongProgramIn
Indicates that an institution or organization offers a particularly high-quality or well-regarded program in a specified field or area.
-
E.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3a48c08190b4677d825fcbfaf9 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.