Triple
T32624576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portage Inlet |
E834018
|
entity |
| Predicate | isNavigationArea |
P14961
|
FINISHED |
| Object | small craft and recreational vessels |
—
|
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: small craft and recreational vessels | Statement: [Portage Inlet, isNavigationArea, small craft and recreational vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigationArea Context triple: [Portage Inlet, isNavigationArea, small craft and recreational vessels]
-
A.
hasNavigationArea
Indicates that an entity is associated with or includes a designated area intended for navigation or movement.
-
B.
navigationArea
chosen
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
C.
isNavigableVia
Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
-
D.
isNavigationStar
Indicates that one entity serves as a guiding or reference star used for navigation relative to another entity.
-
E.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.