Triple
T29524237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Anchorage Seawolves |
E749019
|
entity |
| Predicate | volleyballLevel |
P5182
|
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, volleyballLevel, NCAA Division II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volleyballLevel Context triple: [Alaska Anchorage Seawolves, volleyballLevel, NCAA Division II]
-
A.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
B.
coachesLevel
Indicates the level or tier at which one entity coaches another, such as their rank, division, or proficiency category in a coaching context.
-
C.
teamLevel
chosen
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
D.
governsSportLevel
Indicates that one entity has authority to set, control, or regulate the competitive level or tier at which a sport or sporting activity is conducted.
-
E.
associatedLeagueLevel
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
- 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.