Triple
T19524575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sound of Scalpay |
E488486
|
entity |
| Predicate | isNavigableWaterway |
P95304
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sound of Scalpay, isNavigableWaterway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigableWaterway Context triple: [Sound of Scalpay, isNavigableWaterway, true]
-
A.
isWaterway
chosen
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
B.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
C.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
D.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
E.
stateWaterway
Indicates that a waterway is located within, passes through, or is otherwise geographically associated with a particular state.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63639cfc08190894ac67f7d861a25 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.