Triple
T19252363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune’s Bellows |
E481424
|
entity |
| Predicate | hasNavigationRequirement |
P47583
|
FINISHED |
| Object | careful pilotage |
—
|
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: careful pilotage | Statement: [Neptune’s Bellows, hasNavigationRequirement, careful pilotage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationRequirement Context triple: [Neptune’s Bellows, hasNavigationRequirement, careful pilotage]
-
A.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
hasNavigationRoute
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
-
C.
hasNavigationAccess
Indicates that one entity is permitted to access or use the navigation capabilities or navigation-related resources of another entity.
-
D.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
E.
hasNavigationCharacteristic
chosen
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb31f8ac81909cd9a417b60f86a8 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.