Triple
T20222864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma Christian University |
E495301
|
entity |
| Predicate | relocatedToOklahomaCityYear |
P122122
|
FINISHED |
| Object | 1958 |
—
|
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: 1958 | Statement: [Oklahoma Christian University, relocatedToOklahomaCityYear, 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedToOklahomaCityYear Context triple: [Oklahoma Christian University, relocatedToOklahomaCityYear, 1958]
-
A.
relocationYearToTulsa
Indicates the year in which an entity moved or was relocated to Tulsa.
-
B.
endYearInOklahomaCity
Indicates that the entity’s final or ending year of activity, existence, or relevance occurred in Oklahoma City.
-
C.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
-
D.
startYearInOklahomaCity
chosen
Indicates the year in which the referenced entity began its presence, activity, or operation in Oklahoma City.
-
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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd729548190942bcf842f03c4cd |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.