Triple
T17381085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Coeur d'Alene Resort Golf Course |
E422567
|
entity |
| Predicate | hasHole |
P68170
|
FINISHED |
| Object | par-3 14th hole |
—
|
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 14th hole | Statement: [The Coeur d'Alene Resort Golf Course, hasHole, par-3 14th hole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHole Context triple: [The Coeur d'Alene Resort Golf Course, hasHole, par-3 14th hole]
-
A.
hasHoleCount
Indicates that an entity possesses a specified number of holes.
-
B.
hasHoleShape
Indicates that an entity possesses a hole or opening characterized by a specific geometric or structural shape.
-
C.
hasHoleVariety
Indicates that one entity possesses or exhibits a particular type or variety of hole.
-
D.
numberOfHoles
Indicates the count of holes associated with or present in a given entity.
-
E.
hasHoleName
chosen
Indicates that an entity (such as a golf course or layout) has a specific hole identified by a particular name.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a860f588190915e0671f44bfbcc |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.