Triple
T31640737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Eil |
E807446
|
entity |
| Predicate | hasOutwardBoundCentre |
P175470
|
FINISHED |
| Object | Outward Bound Loch Eil |
—
|
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: Outward Bound Loch Eil | Statement: [Loch Eil, hasOutwardBoundCentre, Outward Bound Loch Eil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutwardBoundCentre Context triple: [Loch Eil, hasOutwardBoundCentre, Outward Bound Loch Eil]
-
A.
isCentreOf
Indicates that one entity serves as the central point, core, or focal location relative to another entity or context.
-
B.
hasBarycenter
Indicates that one entity serves as the barycenter (center of mass) of another entity or system.
-
C.
hasCenterIn
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
D.
hasOutletCenterFeature
Indicates that an entity possesses a characteristic, attribute, or component related to an outlet center.
-
E.
hasTrailCentre
Indicates that a location or area contains or is served by a designated trail centre that provides access to and facilities for trails.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: April 30, 2026, 10:49 p.m.