Triple
T20604687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Inlet |
E506272
|
entity |
| Predicate | hasNavigationAccessTo |
P35064
|
FINISHED |
| Object | open Pacific Ocean |
—
|
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: open Pacific Ocean | Statement: [Portland Inlet, hasNavigationAccessTo, open Pacific Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationAccessTo Context triple: [Portland Inlet, hasNavigationAccessTo, open Pacific Ocean]
-
A.
hasNavigationAccess
chosen
Indicates that one entity is permitted to access or use the navigation capabilities or navigation-related resources of another entity.
-
B.
hasAccessRouteTo
Indicates that one entity possesses a path, connection, or means of reaching or interacting with another entity.
-
C.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
D.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
E.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa233e1881908749d2f29c2946e4 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.