Triple
T3070765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Cinque Ports Golf Club |
E64013
|
entity |
| Predicate | courseStyle |
P44259
|
FINISHED |
| Object | traditional out-and-back links |
—
|
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: traditional out-and-back links | Statement: [Royal Cinque Ports Golf Club, courseStyle, traditional out-and-back links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseStyle Context triple: [Royal Cinque Ports Golf Club, courseStyle, traditional out-and-back links]
-
A.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
B.
courseShape
Indicates the geometric layout or configuration that defines the path or outline of a course.
-
C.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
-
D.
courseDirection
Indicates the orientation or path that something follows or is intended to follow, such as the direction of movement, flow, or progression.
-
E.
courseStructure
Indicates how a course is organized into its constituent parts, such as modules, units, lessons, and their sequencing or hierarchy.
- 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.