Triple
T22910616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cypress Point Club |
E568578
|
entity |
| Predicate | golfCourseLength |
P150205
|
FINISHED |
| Object | approximately 6,500–6,600 yards (varies by tee) |
—
|
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: approximately 6,500–6,600 yards (varies by tee) | Statement: [Cypress Point Club, golfCourseLength, approximately 6,500–6,600 yards (varies by tee)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: golfCourseLength Context triple: [Cypress Point Club, golfCourseLength, approximately 6,500–6,600 yards (varies by tee)]
-
A.
turfCourseDistance
Indicates the distance over which an event or action occurs on a turf (grass) course.
-
B.
golfCoursePar
Indicates the standard number of strokes a skilled golfer is expected to take to complete a particular golf course or hole.
-
C.
numberOfGolfCourses
Indicates the total count of golf courses associated with a given entity.
-
D.
golfCourseUse
Indicates that an entity is used as a golf course or for playing golf.
-
E.
golfCourseStyle
Indicates the design or architectural style that characterizes a particular golf course.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807493a881909e7ee6e8c4c5d4ad |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:42 p.m.