Triple
T3363524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Lautoka |
E70778
|
entity |
| Predicate | hasNavigationCharacteristic |
P47583
|
FINISHED |
| Object | deep-water access |
—
|
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: deep-water access | Statement: [Port of Lautoka, hasNavigationCharacteristic, deep-water access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationCharacteristic Context triple: [Port of Lautoka, hasNavigationCharacteristic, deep-water access]
-
A.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
C.
hasNavigationAccess
Indicates that one entity is permitted to access or use the navigation capabilities or navigation-related resources of another entity.
-
D.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
E.
hasNavigationClass
Indicates that an entity is assigned to, or associated with, a particular navigation-related classification or category.
- F. None of above. chosen
Provenance (4 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26a5a508190948932769de0dbb3 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:13 p.m.