Triple
T33262605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wichita Wind Surge |
E851555
|
entity |
| Predicate | previousPlannedLeague |
P72004
|
FINISHED |
| Object | Pacific Coast League |
—
|
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: Pacific Coast League | Statement: [Wichita Wind Surge, previousPlannedLeague, Pacific Coast League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPlannedLeague Context triple: [Wichita Wind Surge, previousPlannedLeague, Pacific Coast League]
-
A.
previousHomeLeague
Indicates that a specified league was the one in which an entity (such as a team or player) most recently competed before its current league.
-
B.
previousLeagueNameContext
Indicates that the predicate specifies the contextual information or circumstances under which a league previously had a particular name.
-
C.
previousCompetition
Indicates that one competition occurred before another in time.
-
D.
predecessorStateLeague
chosen
Indicates that one league served as the previous or former league organization before the current league.
-
E.
previousSeason
Indicates that one season directly precedes another in chronological order within the same series or competition.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:32 a.m.