Triple
T16982950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twofold Bay |
E411989
|
entity |
| Predicate | isNavigationPointFor |
P11053
|
FINISHED |
| Object | coastal shipping routes |
—
|
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: coastal shipping routes | Statement: [Twofold Bay, isNavigationPointFor, coastal shipping routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigationPointFor Context triple: [Twofold Bay, isNavigationPointFor, coastal shipping routes]
-
A.
isNavigationStar
Indicates that one entity serves as a guiding or reference star used for navigation relative to another entity.
-
B.
isReferencePointFor
chosen
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
isOnNavigation
Indicates that one entity is currently located on, or actively using, a navigation interface, route, or control associated with another entity.
-
D.
isNavigableNear
Indicates that an entity can be traversed or passed through in close proximity to another specified entity or location.
-
E.
isPointWhere
Indicates that one entity is the specific location or point at which another entity, event, or condition occurs or is defined.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d188ede48190baead48aac84c78d |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.