Triple
T23479563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaforth Island |
E570365
|
entity |
| Predicate | locatedInSeaLoch |
P103956
|
FINISHED |
| Object | Loch Seaforth |
—
|
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: Loch Seaforth | Statement: [Seaforth Island, locatedInSeaLoch, Loch Seaforth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSeaLoch Context triple: [Seaforth Island, locatedInSeaLoch, Loch Seaforth]
-
A.
hasLoch
Indicates that one entity possesses, contains, or features a loch (lake or sea inlet) as part of its characteristics or composition.
-
B.
locatedAtSea
Indicates that something exists or is situated in or on the sea.
-
C.
locatedInHarbourArea
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
-
D.
locatedInBayOf
Indicates that something is situated within or directly on a specific bay.
-
E.
associatedLoch
chosen
Indicates that one entity is linked or connected to a particular loch (lake or sea inlet), typically by location, relevance, or contextual relationship.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74f48d8819080e875aaea8b46b3 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:02 p.m.