Triple
T38192773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nairn Golf Club |
E1005516
|
entity |
| Predicate | fairwaysBorder |
P190275
|
FINISHED |
| Object | beach |
—
|
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: beach | Statement: [Nairn Golf Club, fairwaysBorder, beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fairwaysBorder Context triple: [Nairn Golf Club, fairwaysBorder, beach]
-
A.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
B.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
C.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
D.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
bordersFacility
Indicates that one facility or site lies directly adjacent to and shares a boundary with another facility.
- F. None of above. chosen
Provenance (4 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:29 p.m.