Triple
T32408574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royals |
E828149
|
entity |
| Predicate | previousLeagueIdentity |
P94559
|
FINISHED |
| Object | ECHL Columbus Chill |
—
|
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: ECHL Columbus Chill | Statement: [Royals, previousLeagueIdentity, ECHL Columbus Chill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLeagueIdentity Context triple: [Royals, previousLeagueIdentity, ECHL Columbus Chill]
-
A.
previousLeagueNameContext
Indicates that the predicate specifies the contextual information or circumstances under which a league previously had a particular name.
-
B.
leaguePredecessor
Indicates that one league existed before and was replaced or succeeded by another league in an organizational or historical sequence.
-
C.
predecessorStateLeague
Indicates that one league served as the previous or former league organization before the current league.
-
D.
previousHomeLeague
chosen
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.
-
E.
predecessorLeagueContext
Indicates that one league serves as the direct predecessor or prior contextual version of another league within 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 12:53 a.m.