Triple
T24021025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wentworth Club |
E594820
|
entity |
| Predicate | hasParEastCourse |
P154887
|
FINISHED |
| Object | 68 |
—
|
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: 68 | Statement: [Wentworth Club, hasParEastCourse, 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParEastCourse Context triple: [Wentworth Club, hasParEastCourse, 68]
-
A.
hasParCourse
Indicates that an entity is associated with, or includes, a specific par course (an exercise or fitness trail with designated stations).
-
B.
hasCoursePar
Indicates that one course is a parent or higher-level course in relation to another course, such as a prerequisite or overarching course.
-
C.
hasInnerTurfCourse
Indicates that something (typically a race track or stadium) possesses an inner turf course located within its main track or field.
-
D.
parOfChampionshipCourse
Indicates that one entity is a part or segment of a championship course associated with another entity.
-
E.
hasProAm
Indicates that an entity possesses or is associated with a professional–amateur (pro-am) status, feature, or component.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:43 p.m.