Triple
T27389223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathblane |
E691472
|
entity |
| Predicate | hasNotableNaturalFeatureNearby |
P194420
|
FINISHED |
| Object | Campsie Fells |
—
|
NE NERFINISHED |
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: Campsie Fells | Statement: [Strathblane, hasNotableNaturalFeatureNearby, Campsie Fells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNaturalFeatureNearby Context triple: [Strathblane, hasNotableNaturalFeatureNearby, Campsie Fells]
-
A.
hasNaturalAttractionsNearby
chosen
Indicates that a place is located near or surrounded by notable natural attractions or scenic natural features.
-
B.
hasNaturalParkNearby
Indicates that one entity is located close to, or in the vicinity of, a natural park associated with the other entity.
-
C.
hasNotableNearbyMountain
Indicates that an entity is located near and is notably associated with a particular mountain.
-
D.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
E.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 27, 2026, 12:25 p.m.