Triple
T32325398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alps (17th hole) |
E825896
|
entity |
| Predicate | visibilityFromFairway |
P147891
|
FINISHED |
| Object | green not directly visible over dune |
—
|
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: green not directly visible over dune | Statement: [Alps (17th hole), visibilityFromFairway, green not directly visible over dune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityFromFairway Context triple: [Alps (17th hole), visibilityFromFairway, green not directly visible over dune]
-
A.
isDifficultToSeeFrom
chosen
Indicates that one entity is hard to visually perceive or observe when viewed from the vantage point or location of another entity.
-
B.
fairwayType
Indicates the specific kind or classification of a fairway associated with an entity.
-
C.
visibilityFromSea
Indicates that something can be seen or is visually detectable when viewed from the sea.
-
D.
visibilitySector
Indicates the angular region or sector within which something is visible from a given point or direction.
-
E.
visibleYearRoundFrom
Indicates that one entity can be seen throughout the entire year from the location or vantage point of another entity.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde7cd8481908d3128d089c86c14 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:47 a.m.