Triple
T8052213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claggan Park, Fort William |
E187700
|
entity |
| Predicate | usedAsFinishPointFor |
P54395
|
FINISHED |
| Object | mountain races on Ben Nevis |
—
|
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: mountain races on Ben Nevis | Statement: [Claggan Park, Fort William, usedAsFinishPointFor, mountain races on Ben Nevis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFinishPointFor Context triple: [Claggan Park, Fort William, usedAsFinishPointFor, mountain races on Ben Nevis]
-
A.
formerFinishLocation
chosen
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
B.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
C.
basedInUntil
Indicates that an entity was based or located in a particular place up to a specified end time or date, after which this association ceased.
-
D.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
-
E.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7aab6481909d4a7cb9eabcd2af |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.