Triple
T32325397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alps (17th hole) |
E825896
|
entity |
| Predicate | visibilityFromTee |
P9694
|
FINISHED |
| Object | fairway partially visible |
—
|
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: fairway partially visible | Statement: [Alps (17th hole), visibilityFromTee, fairway partially visible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityFromTee Context triple: [Alps (17th hole), visibilityFromTee, fairway partially visible]
-
A.
isDifficultToSeeFrom
Indicates that one entity is hard to visually perceive or observe when viewed from the vantage point or location of another entity.
-
B.
visibleBy
Indicates that one entity can be seen or perceived visually by another entity.
-
C.
visibilityFromSea
Indicates that something can be seen or is visually detectable when viewed from the sea.
-
D.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
E.
visibleAt
chosen
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
- 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_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:47 a.m.