Triple
T29524236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Anchorage Seawolves |
E749019
|
entity |
| Predicate | basketballLevel |
P21979
|
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, basketballLevel, NCAA Division II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basketballLevel Context triple: [Alaska Anchorage Seawolves, basketballLevel, NCAA Division II]
-
A.
hasBasketballLevel
chosen
Indicates that an entity possesses a specified level of skill, proficiency, or ranking in basketball.
-
B.
roleInBasketball
Indicates the specific function or position an entity holds within the context of playing or organizing a game of basketball.
-
C.
leagueLevelRelativeToNBA
Indicates the comparative competitive level or tier of a basketball league in relation to the NBA.
-
D.
usesBasketball
Indicates that one entity makes use of or engages with basketball, typically as equipment or in the context of playing the sport.
-
E.
basketballNationalTitle
Indicates that an entity has won a national championship title in the sport of basketball.
- 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_69f66c9b32948190a6911e19d7b83b7e |
completed | May 2, 2026, 9:28 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:44 p.m.