Triple
T15394663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanin Nos Cape |
E368141
|
entity |
| Predicate | hasNavigationSignificance |
P47583
|
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: [Kanin Nos Cape, hasNavigationSignificance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationSignificance Context triple: [Kanin Nos Cape, hasNavigationSignificance, true]
-
A.
hasNavigationPurpose
Indicates that something exists or is designed specifically to serve a navigational function or goal.
-
B.
hasNavigationCharacteristic
chosen
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
C.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
D.
hasNavigationPass
Indicates that an entity possesses a valid authorization or pass granting it navigation or passage rights within a specified area or route.
-
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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.