Triple
T10511685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulsa Shock |
E247929
|
entity |
| Predicate | relocationAnnounced |
P94305
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Tulsa Shock, relocationAnnounced, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationAnnounced Context triple: [Tulsa Shock, relocationAnnounced, 2015]
-
A.
relocationAnnouncedBy
Indicates that the relocation of something (such as a person, organization, or asset) was publicly communicated or made known by a particular agent or source.
-
B.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
C.
requiredRelocationFrom
Indicates that one entity mandates or necessitates the relocation of another entity away from a specified source location or context.
-
D.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
E.
relocationStart
Indicates the point in time or event at which a relocation process for an entity begins.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b5fcb8819087a23a2b26aecd70 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:27 p.m.