Triple
T18641120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Elmo |
E455686
|
entity |
| Predicate | targetClassYear |
P52828
|
FINISHED |
| Object | rising seniors |
—
|
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: rising seniors | Statement: [St. Elmo, targetClassYear, rising seniors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetClassYear Context triple: [St. Elmo, targetClassYear, rising seniors]
-
A.
typicalClassYear
Indicates the usual or expected academic year level associated with an entity, such as when a course is typically taken or a program is normally completed.
-
B.
schoolYear
chosen
Indicates the academic year or grade level in which an entity (typically a student or class) is situated within an educational system.
-
C.
recruitingClassYear
Indicates the year associated with an entity’s recruiting class, typically specifying when a person is expected to join or start with a team, program, or organization.
-
D.
matriculationYear
Indicates the calendar year in which an individual formally enrolled or was admitted into an educational program or institution.
-
E.
applicationYear
Indicates the year in which an application was submitted or made.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fccafec8190a340356d5bbd3cdf |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.