Triple
T35606688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladhar Bheinn |
E1028911
|
entity |
| Predicate | regionForMunroists |
P201153
|
FINISHED |
| Object | Loch Hourn to Loch Quoich |
—
|
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: Loch Hourn to Loch Quoich | Statement: [Ladhar Bheinn, regionForMunroists, Loch Hourn to Loch Quoich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionForMunroists Context triple: [Ladhar Bheinn, regionForMunroists, Loch Hourn to Loch Quoich]
-
A.
onlyMunroOn
Indicates that the referenced mountain is the sole Munro located on the specified island or landmass.
-
B.
hasNearbyMunro
Indicates that one location is situated close to a Munro (a Scottish mountain over 3,000 feet).
-
C.
hasNearbyMunroTop
Indicates that an entity has a Munro Top located in close geographic proximity to it.
-
D.
hasNumberOfMunros
Indicates the relationship that specifies how many Munros (Scottish mountains over 3,000 feet) are associated with a given entity.
-
E.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
| PDg | Predicate description generation | batch_69ffcc60dae48190b76b3eb7e2ce5103 |
completed | May 10, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:05 p.m.