Triple
T18642064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Genesis Invitational |
E455712
|
entity |
| Predicate | establishedAsTournamentAtRiviera |
P58332
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [The Genesis Invitational, establishedAsTournamentAtRiviera, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsTournamentAtRiviera Context triple: [The Genesis Invitational, establishedAsTournamentAtRiviera, 1929]
-
A.
firstKnownTournament
Indicates the earliest tournament in which the entity is known or recorded to have participated or appeared.
-
B.
firstTournamentHost
Indicates that the subject entity is the first host of a particular tournament or competition.
-
C.
precededByTournament
Indicates that one event or entity occurs after and is directly preceded by a specific tournament.
-
D.
firstKnownTournamentYear
chosen
Indicates the year in which a tournament was first known to have been held.
-
E.
hasFinalTournament
Indicates that an entity is associated with a specific tournament that serves as its final or concluding competition.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcd6da081908030b052727f2c2f |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.