Triple
T25586801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Cardinals |
E641406
|
entity |
| Predicate | revertedLeagueName |
P159146
|
FINISHED |
| Object | Texas League (from 2022) |
—
|
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: Texas League (from 2022) | Statement: [Springfield Cardinals, revertedLeagueName, Texas League (from 2022)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revertedLeagueName Context triple: [Springfield Cardinals, revertedLeagueName, Texas League (from 2022)]
-
A.
rejoinedLeagueName
Indicates that an entity has returned to and become a member again of a previously left league identified by its name.
-
B.
leagueRenamedAs
Indicates that a sports league has changed its official name to a new one.
-
C.
previousLeagueNameUsage
Indicates that an entity previously used a different league name during an earlier period or context.
-
D.
formerLeagueNameFor
Indicates that one league name was previously used for, but has since been replaced by, the current name of a league.
-
E.
laterLeagueName
Indicates that an entity’s league name was changed to a different (later) league name at some point in time.
- F. None of above. chosen
Provenance (4 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96a44bc8190a38439dbc297ebc5 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 4:17 p.m.