Triple
T19693598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blue Monster |
E472895
|
entity |
| Predicate | waterHazardsAffect |
P69150
|
FINISHED |
| Object | multiple 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: multiple holes | Statement: [The Blue Monster, waterHazardsAffect, multiple holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterHazardsAffect Context triple: [The Blue Monster, waterHazardsAffect, multiple holes]
-
A.
hasWaterHazards
chosen
Indicates that the subject contains or is associated with one or more water-based obstacles or danger areas.
-
B.
hasLakeOnCourse
Indicates that a course (such as a route or path) includes at least one lake situated along its way or within its boundaries.
-
C.
notableHole
Indicates that an entity has a hole or opening that is significant or noteworthy in some context.
-
D.
fairwayType
Indicates the specific kind or classification of a fairway associated with an entity.
-
E.
8thHolePar
Indicates that the par (expected number of strokes) is specified for the 8th hole of a golf course.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64211e5d481908358d922e0dca271 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.