Triple
T4057603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Admirals |
E84730
|
entity |
| Predicate | leagueMove |
P19402
|
FINISHED |
| Object | franchise moved from AHL to ECHL structure |
—
|
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: franchise moved from AHL to ECHL structure | Statement: [Norfolk Admirals, leagueMove, franchise moved from AHL to ECHL structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueMove Context triple: [Norfolk Admirals, leagueMove, franchise moved from AHL to ECHL structure]
-
A.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
B.
movedToLeague
chosen
Indicates that an entity changed affiliation or membership from one league to another.
-
C.
teamRelocatedResult
Indicates that a sports team has changed its home location and specifies the outcome or status resulting from that relocation.
-
D.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
-
E.
leagueRenamedAs
Indicates that a sports league has changed its official name to a new one.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbaefcb081908aab3963dcd61a20 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.