Triple
T30398484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunningdale Golf Club |
E773284
|
entity |
| Predicate | hasTournamentHistory |
P72801
|
FINISHED |
| Object | Open Championship qualifying |
—
|
NE NERFINISHED |
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: Open Championship qualifying | Statement: [Sunningdale Golf Club, hasTournamentHistory, Open Championship qualifying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTournamentHistory Context triple: [Sunningdale Golf Club, hasTournamentHistory, Open Championship qualifying]
-
A.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
-
B.
hasCompetitionHistory
chosen
Indicates that an entity has a recorded history of participation in competitions or competitive events.
-
C.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
D.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
-
E.
hasTourHistory
Indicates that an entity has a record of past tours or tour-related activities.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.