Triple
T3070706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal St George’s Golf Club |
E64012
|
entity |
| Predicate | hasCoursePar |
P44256
|
FINISHED |
| Object | 70 |
—
|
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: 70 | Statement: [Royal St George’s Golf Club, hasCoursePar, 70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoursePar Context triple: [Royal St George’s Golf Club, hasCoursePar, 70]
-
A.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
B.
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).
-
C.
playedOnCourse
Indicates that an entity (typically a player or team) participated in a game, match, or round that took place on a specific course.
-
D.
typicalCoursePar
Indicates that one course is a typical or standard parallel (i.e., alternative but equivalent) course to another within a curriculum or program.
-
E.
usesCourse
Indicates that one entity makes use of, applies, or relies on a particular course in some context or activity.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f7630c81908e1ca8a69611cff6 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.