Triple
T26054641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spokane Comets |
E648082
|
entity |
| Predicate | franchiseMoveDestination |
P36297
|
FINISHED |
| Object | Portland, Oregon |
—
|
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: Portland, Oregon | Statement: [Spokane Comets, franchiseMoveDestination, Portland, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseMoveDestination Context triple: [Spokane Comets, franchiseMoveDestination, Portland, Oregon]
-
A.
franchiseRelocatedFrom
Indicates that a sports or business franchise has moved its operations or home base away from a specified previous location.
-
B.
franchiseShift
Indicates a change or transfer in control, ownership, or primary association of a franchise from one party or context to another.
-
C.
franchiseChange
Indicates a change in the ownership, control, or branding rights of a franchise from one party to another.
-
D.
associatedWithFranchiseMove
Indicates a relationship where an entity is connected to or involved in the relocation or transfer of a franchise from one place or ownership context to another.
-
E.
teamRelocationTo
chosen
Indicates the movement of a team from one location to another as its new home or base of operations.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 9:11 a.m.