Triple
T37868868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cog Hill Golf and Country Club |
E944550
|
entity |
| Predicate | tourTypeHosted |
P189310
|
FINISHED |
| Object | PGA Tour |
—
|
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 Tour | Statement: [Cog Hill Golf and Country Club, tourTypeHosted, PGA Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourTypeHosted Context triple: [Cog Hill Golf and Country Club, tourTypeHosted, PGA Tour]
-
A.
tourWin
Indicates that an entity wins or is victorious in a tour, tournament, or competitive series of events.
-
B.
hostedAttraction
Indicates that an entity served as the venue or location where a particular attraction, event, or feature was presented or took place.
-
C.
tourCategory
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
-
D.
tourismEvent
Indicates an event or activity that is organized for or significantly involves tourism, attracting visitors for leisure, cultural, or recreational purposes.
-
E.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
- F. None of above. chosen
Provenance (4 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.