Triple
T4833676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Fox course |
E108005
|
entity |
| Predicate | waterHazards |
P56309
|
FINISHED |
| Object | present on many holes |
—
|
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: present on many holes | Statement: [Silver Fox course, waterHazards, present on many holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterHazards Context triple: [Silver Fox course, waterHazards, present on many holes]
-
A.
fairwayType
Indicates the specific kind or classification of a fairway associated with an entity.
-
B.
notableHole
Indicates that an entity has a hole or opening that is significant or noteworthy in some context.
-
C.
waterbodyOnCourse
chosen
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
-
D.
hasYardage
Indicates that something possesses or is associated with a specific measured distance or length, typically expressed in yards.
-
E.
ballCondition
Indicates the specific state or status a ball is in, such as its physical condition, readiness for use, or compliance with required standards.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.