Triple
T29524239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Anchorage Seawolves |
E749019
|
entity |
| Predicate | trackAndFieldLevel |
P101309
|
FINISHED |
| Object | NCAA Division II |
—
|
NE NERFINISHED |
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: NCAA Division II | Statement: [Alaska Anchorage Seawolves, trackAndFieldLevel, NCAA Division II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackAndFieldLevel Context triple: [Alaska Anchorage Seawolves, trackAndFieldLevel, NCAA Division II]
-
A.
worldAthleticsLabel
Indicates that an entity is identified by a specific label or designation as defined by World Athletics.
-
B.
playsCollegeTrackAndField
Indicates that an individual participates as an athlete in college-level track and field competitions.
-
C.
sportsLevel
Indicates the degree or intensity of involvement, skill, or competitiveness associated with a sport or sporting activity.
-
D.
levelOfCompetitionAdministered
chosen
Indicates the specific competitive tier or intensity at which an activity, event, or process is formally managed or overseen.
-
E.
athleticsClassification
Indicates the competitive sports category or class assigned to an entity based on defined athletic criteria or rules.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 4:44 p.m.