Triple
T9871904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prestwick Golf Club |
E239975
|
entity |
| Predicate | hasChampionshipHistory |
P65498
|
FINISHED |
| Object | early Open Championship venue |
—
|
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: early Open Championship venue | Statement: [Prestwick Golf Club, hasChampionshipHistory, early Open Championship venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipHistory Context triple: [Prestwick Golf Club, hasChampionshipHistory, early Open Championship venue]
-
A.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
hasWorldChampionship
Indicates that an entity possesses, has won, or holds a world championship title or status.
-
C.
hasTeamsChampionship
Indicates that an entity has won at least one championship title in a teams-based competition or league.
-
D.
hasHistoricFranchise
Indicates that an entity is associated with or possesses a franchise that has historical significance or longstanding legacy.
-
E.
hasChampionshipGames
chosen
Indicates that an entity includes, hosts, or is associated with one or more championship-level games or matches.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f5cc948190b03186b867c92229 |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.