Triple
T32565119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potsy Clark |
E832339
|
entity |
| Predicate | teamRelocationInvolved |
P77279
|
FINISHED |
| Object | Portsmouth Spartans relocation to Detroit Lions |
—
|
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: Portsmouth Spartans relocation to Detroit Lions | Statement: [Potsy Clark, teamRelocationInvolved, Portsmouth Spartans relocation to Detroit Lions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRelocationInvolved Context triple: [Potsy Clark, teamRelocationInvolved, Portsmouth Spartans relocation to Detroit Lions]
-
A.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
B.
teamRelocationEvent
chosen
Indicates an event in which a team changes its home location from one place 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.
teamRelocationYear
Indicates the year in which a team moved from one location 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c60c799c81909782f8f67292d642 |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.