Triple
T10235803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wichita Wind Surge |
E243459
|
entity |
| Predicate | hasLeagueStructure |
P25303
|
FINISHED |
| Object | Double-A affiliate system |
—
|
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: Double-A affiliate system | Statement: [Wichita Wind Surge, hasLeagueStructure, Double-A affiliate system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueStructure Context triple: [Wichita Wind Surge, hasLeagueStructure, Double-A affiliate system]
-
A.
leagueStructure
chosen
Indicates how a league is organized, including its divisions, tiers, and the relationships or hierarchy between its constituent groups or competitions.
-
B.
hasTeamStructure
Indicates that an entity is organized into, or associated with, a specific arrangement of teams or team hierarchy.
-
C.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
D.
successorLeagueStructure
Indicates that one league structure directly follows and replaces another in an organizational or temporal sequence.
-
E.
hasSeparateLeagueSystemFor
Indicates that one entity organizes or maintains a distinct, independent league structure specifically for another entity or group.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:22 a.m.