Triple
T33943452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyhawks |
E870227
|
entity |
| Predicate | previousAthleticAssociation |
P61083
|
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: [Skyhawks, previousAthleticAssociation, NCAA Division II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAthleticAssociation Context triple: [Skyhawks, previousAthleticAssociation, NCAA Division II]
-
A.
previousAthleticsAffiliation
chosen
Indicates that an entity formerly had an athletics-related membership, role, or association with another entity, but no longer does.
-
B.
competitionFormerName
Indicates that a competition previously operated under a different name than its current one.
-
C.
leaguePredecessor
Indicates that one league existed before and was replaced or succeeded by another league in an organizational or historical sequence.
-
D.
previousFranchiseCity
Indicates that a city was formerly the home location of a particular franchise before it moved or relocated.
-
E.
clubPredecessorOf
Indicates that one club existed earlier and was replaced or succeeded by another club in an organizational or historical sequence.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 1:49 a.m.