Triple
T624434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Base Pearl Harbor–Hickam |
E14584
|
entity |
| Predicate | hasHarborType |
P6668
|
FINISHED |
| Object | natural deep-water harbor |
—
|
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: natural deep-water harbor | Statement: [Joint Base Pearl Harbor–Hickam, hasHarborType, natural deep-water harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarborType Context triple: [Joint Base Pearl Harbor–Hickam, hasHarborType, natural deep-water harbor]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
harborType
chosen
Indicates the specific kind or classification of a harbor associated with an entity.
-
C.
harbourUse
Indicates how a harbour is used or purposed, such as for specific activities, functions, or types of maritime operations.
-
D.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
E.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e43002c81908e0c7dab29b75978 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.