Triple
T36741747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warren Valley Golf Course |
E907636
|
entity |
| Predicate | hasHoleCountPerCourse |
P8599
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Warren Valley Golf Course, hasHoleCountPerCourse, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHoleCountPerCourse Context triple: [Warren Valley Golf Course, hasHoleCountPerCourse, 18]
-
A.
hasHoleCount
chosen
Indicates that an entity possesses a specified number of holes.
-
B.
numberOfHoles
Indicates the count of holes associated with or present in a given entity.
-
C.
hasNotableHolePar
Indicates that a particular hole on a golf course is especially significant or noteworthy for that player’s performance (e.g., key scoring or memorable play).
-
D.
estimatedHolesInOne
Indicates that a numerical estimate is being made of how many holes-in-one (aces) are expected to occur in a given golf context (such as for a player, round, event, or time period).
-
E.
hasHoleVariety
Indicates that one entity possesses or exhibits a particular type or variety of hole.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:12 p.m.