Triple
T34059263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor's Cup (Kentucky–Louisville) |
E873444
|
entity |
| Predicate | gameLocationPattern |
P178185
|
FINISHED |
| Object | alternates annually between Lexington and Louisville |
—
|
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: alternates annually between Lexington and Louisville | Statement: [Governor's Cup (Kentucky–Louisville), gameLocationPattern, alternates annually between Lexington and Louisville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameLocationPattern Context triple: [Governor's Cup (Kentucky–Louisville), gameLocationPattern, alternates annually between Lexington and Louisville]
-
A.
gameLocation
Indicates the place or venue where a game or match takes place.
-
B.
game4Location
Indicates the place or venue where the fourth game in a series or sequence takes place.
-
C.
game2Location
Indicates that a game takes place at, or is associated with, a specific location.
-
D.
Game6Location
Indicates the location where the sixth game in a series or sequence takes place.
-
E.
game1Location
Indicates the physical or virtual place where the first game is held or takes place.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:52 a.m.