Triple
T24843859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rousay Sound |
E621687
|
entity |
| Predicate | hasMaritimeUse |
P7788
|
FINISHED |
| Object | navigation route |
—
|
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: navigation route | Statement: [Rousay Sound, hasMaritimeUse, navigation route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeUse Context triple: [Rousay Sound, hasMaritimeUse, navigation route]
-
A.
maritimeUsage
chosen
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
B.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
C.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
D.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
E.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 5:19 a.m.