Triple
T17304956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westchester Country Club |
E420136
|
entity |
| Predicate | hasCourseUse |
P21769
|
FINISHED |
| Object | professional tournaments |
—
|
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: professional tournaments | Statement: [Westchester Country Club, hasCourseUse, professional tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourseUse Context triple: [Westchester Country Club, hasCourseUse, professional tournaments]
-
A.
usesCourse
chosen
Indicates that one entity makes use of, applies, or relies on a particular course in some context or activity.
-
B.
courseUse
Indicates that a course employs, incorporates, or makes use of a particular resource, tool, or material in its instruction or structure.
-
C.
hasHostCourse
Indicates that one entity serves as the primary or organizing course responsible for hosting or containing another related course or course component.
-
D.
hasCoursePattern
Indicates that an entity follows, is associated with, or is defined by a particular course structure or pattern.
-
E.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fe1d408190a429d1dba50d0c58 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.