Triple
T26204220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pebble Beach Golf Links |
E655316
|
entity |
| Predicate | hasHostedTournament |
P74099
|
FINISHED |
| Object | PGA Championship 1977 |
—
|
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: PGA Championship 1977 | Statement: [Pebble Beach Golf Links, hasHostedTournament, PGA Championship 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostedTournament Context triple: [Pebble Beach Golf Links, hasHostedTournament, PGA Championship 1977]
-
A.
hasHostedSport
Indicates that a place or organization has served as the venue or organizer for one or more sporting events.
-
B.
hasTournament
chosen
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
C.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
-
D.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
E.
hasHostedVenue
Indicates that a particular venue has served as the location for hosting a specific event or activity.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 8:50 p.m.