Triple
T24882658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craigend Course |
E622753
|
entity |
| Predicate | isAdditionalCourseOf |
P157435
|
FINISHED |
| Object | Royal Troon Golf Club |
—
|
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: Royal Troon Golf Club | Statement: [Craigend Course, isAdditionalCourseOf, Royal Troon Golf Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdditionalCourseOf Context triple: [Craigend Course, isAdditionalCourseOf, Royal Troon Golf Club]
-
A.
isCourse
Indicates that an entity functions as or qualifies as a course within a given context or system.
-
B.
hasSisterCourse
Indicates that one course is related to another as a sister course, typically sharing similar content, level, or structure within the same curriculum or program.
-
C.
associatedCourse
Indicates that one entity is linked or connected to a particular course in a relevant or contextual way.
-
D.
hasMultipleCourses
Indicates that an entity is associated with more than one course within the given context.
-
E.
hasPrimaryCourse
Indicates that an entity is associated with its main or principal course in a given context (such as a meal, curriculum, or sequence of offerings).
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:24 a.m.