Triple
T2975030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahaina |
E80373
|
entity |
| Predicate | harborUsedFor |
P12053
|
FINISHED |
| Object | whale-watching tours |
—
|
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: whale-watching tours | Statement: [Lahaina, harborUsedFor, whale-watching tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harborUsedFor Context triple: [Lahaina, harborUsedFor, whale-watching tours]
-
A.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
-
B.
harborOwnership
Indicates that one entity possesses legal or recognized ownership rights over a harbor or port facility.
-
C.
harborManagedBy
Indicates that the operation, administration, or oversight of a harbor is carried out by a specified managing entity.
-
D.
harbourUse
chosen
Indicates how a harbour is used or purposed, such as for specific activities, functions, or types of maritime operations.
-
E.
harborRole
Indicates that an entity serves in a particular capacity, function, or role within a specified context or relationship.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99894bb0819099fa5cc5166c0eeb |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.