Triple
T11090504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbarns Golf Links |
E262237
|
entity |
| Predicate | notableHoleFeature |
P46334
|
FINISHED |
| Object | par-3 holes playing along the sea |
—
|
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: par-3 holes playing along the sea | Statement: [Kingsbarns Golf Links, notableHoleFeature, par-3 holes playing along the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHoleFeature Context triple: [Kingsbarns Golf Links, notableHoleFeature, par-3 holes playing along the sea]
-
A.
notableHole
Indicates that an entity has a hole or opening that is significant or noteworthy in some context.
-
B.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
D.
8thHoleName
Indicates the name assigned to the eighth hole in a golf course or similar sequential layout.
-
E.
notableDrill
Indicates that an entity is recognized as a significant or noteworthy drill, exercise, or practice activity in a given context.
- F. None of above.
Provenance (3 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799e96ca08190838c8a04d1eb2a16 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.