Triple
T24664404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochranza Golf Course |
E610629
|
entity |
| Predicate | landscapeView |
P156938
|
FINISHED |
| Object | coastline |
—
|
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: coastline | Statement: [Lochranza Golf Course, landscapeView, coastline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeView Context triple: [Lochranza Golf Course, landscapeView, coastline]
-
A.
landscapeView
chosen
Indicates that one entity provides or features a scenic or panoramic view of a landscape from the perspective of another entity.
-
B.
landscapeStyle
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
-
C.
landscapeValue
Indicates the assessed aesthetic, cultural, or ecological worth attributed to a particular landscape or scenery.
-
D.
landscapeEffect
Indicates how a particular landscape or terrain influences or modifies the outcome, behavior, or characteristics of another entity or process.
-
E.
landscapeAbstraction
Indicates that one entity is an abstract or non-literal representation derived from the landscape or its features.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:34 a.m.