Triple
T23270201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeville Makai Golf Club |
E588265
|
entity |
| Predicate | 7thHoleFeature |
P151620
|
FINISHED |
| Object | plays along ocean cliffs |
—
|
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: plays along ocean cliffs | Statement: [Princeville Makai Golf Club, 7thHoleFeature, plays along ocean cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 7thHoleFeature Context triple: [Princeville Makai Golf Club, 7thHoleFeature, plays along ocean cliffs]
-
A.
8thHoleName
Indicates the name assigned to the eighth hole in a golf course or similar sequential layout.
-
B.
8thHolePar
Indicates that the par (expected number of strokes) is specified for the 8th hole of a golf course.
-
C.
notableHole
Indicates that an entity has a hole or opening that is significant or noteworthy in some context.
-
D.
16thHolePar
Indicates that the par (expected number of strokes) is being specified for the 16th hole of a golf course.
-
E.
16thHoleDescription
Indicates a descriptive relationship that specifies notable features, layout, or characteristics of the 16th hole in a course or sequence.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957324bc8190b8b53d4b18386151 |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:45 p.m.