Triple
T3070715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal St George’s Golf Club |
E64012
|
entity |
| Predicate | hostedOpenChampionshipIn |
P35512
|
FINISHED |
| Object | 1894 |
—
|
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: 1894 | Statement: [Royal St George’s Golf Club, hostedOpenChampionshipIn, 1894]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedOpenChampionshipIn Context triple: [Royal St George’s Golf Club, hostedOpenChampionshipIn, 1894]
-
A.
championshipHeldIn
Indicates that a particular championship event takes place or is hosted in a specific location.
-
B.
sportsEventHosted
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
C.
hostedDiscipline
Indicates that an entity served as the host or venue for a particular discipline, event category, or field of competition.
-
D.
hostedDuring
chosen
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
E.
organizesChampionship
Indicates that an entity is responsible for planning, coordinating, and managing the execution of a championship event.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.