Triple
T19378916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Firebirds |
E484744
|
entity |
| Predicate | notableLeagueTransition |
P19402
|
FINISHED |
| Object | from NAHL to AHL |
—
|
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: from NAHL to AHL | Statement: [Philadelphia Firebirds, notableLeagueTransition, from NAHL to AHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLeagueTransition Context triple: [Philadelphia Firebirds, notableLeagueTransition, from NAHL to AHL]
-
A.
allStarGameNotableChange
Indicates a notable modification or significant event that occurred in relation to an All-Star Game.
-
B.
notableTransferWindow
Indicates that a transfer window (period for player transfers) is regarded as particularly significant or noteworthy in some context.
-
C.
notableLeague
Indicates that there is a significant or prominent league associated with the subject entity.
-
D.
notableCrossoverPlayer
Indicates that a player is notably recognized for successfully transitioning and performing in multiple distinct leagues, sports, or competitive domains.
-
E.
movedToLeague
chosen
Indicates that an entity changed affiliation or membership from one league to another.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5e8e7081908bed3eee1eef4de2 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.