Triple
T28091477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Hills Country Club |
E709963
|
entity |
| Predicate | tournamentCourseUsed |
P113133
|
FINISHED |
| Object | Dinah Shore Tournament Course |
—
|
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: Dinah Shore Tournament Course | Statement: [Mission Hills Country Club, tournamentCourseUsed, Dinah Shore Tournament Course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentCourseUsed Context triple: [Mission Hills Country Club, tournamentCourseUsed, Dinah Shore Tournament Course]
-
A.
parOfChampionshipCourse
Indicates that one entity is a part or segment of a championship course associated with another entity.
-
B.
playedOnCourse
Indicates that an entity (typically a player or team) participated in a game, match, or round that took place on a specific course.
-
C.
tournamentSpecific
Indicates that the relationship, condition, or data applies only within the context of a particular tournament and not generally across other contexts or events.
-
D.
golfCourseUse
chosen
Indicates that an entity is used as a golf course or for playing golf.
-
E.
tourEvent
Indicates an event that is part of a tour, such as a scheduled stop, performance, or appearance within a larger touring itinerary.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:58 p.m.