Triple
T16199021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City Hornets |
E393146
|
entity |
| Predicate | temporaryRelocationDuration |
P51327
|
FINISHED |
| Object | two seasons |
—
|
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: two seasons | Statement: [Oklahoma City Hornets, temporaryRelocationDuration, two seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryRelocationDuration Context triple: [Oklahoma City Hornets, temporaryRelocationDuration, two seasons]
-
A.
temporaryLocation
Indicates that an entity is located at a place for a limited or non-permanent duration.
-
B.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
C.
displacementPeriod
chosen
Indicates the time interval over which an entity is moved or shifted from one position or state to another.
-
D.
redeploymentTime
Indicates the amount of time required to redeploy or reassign a resource, system, or unit from one operational state or location to another.
-
E.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222de2db481908471b9c73d444607 |
completed | April 17, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.