Triple
T38435805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 WNBA season |
E903937
|
entity |
| Predicate | teamRelocationAfterSeason |
P190751
|
FINISHED |
| Object | Detroit Shock |
—
|
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: Detroit Shock | Statement: [2009 WNBA season, teamRelocationAfterSeason, Detroit Shock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRelocationAfterSeason Context triple: [2009 WNBA season, teamRelocationAfterSeason, Detroit Shock]
-
A.
team2RelocationSeason
Indicates the season or time period during which the second team in a relationship was relocated.
-
B.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
C.
teamRelocationYear
Indicates the year in which a team moved from one location to another.
-
D.
team2RelocationYear
Indicates the year in which the second team in a relationship was relocated to a different place or franchise.
-
E.
teamRelocationEvent
Indicates an event in which a team changes its home location from one place to another.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcce7a25848190bdc66efcbc7cae3a |
completed | May 7, 2026, 5:40 p.m. |
Created at: May 3, 2026, 4:31 p.m.