Triple
T23491525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boot Key Harbor |
E570686
|
entity |
| Predicate | hasHarbormaster |
P152584
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Boot Key Harbor, hasHarbormaster, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbormaster Context triple: [Boot Key Harbor, hasHarbormaster, yes]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasHarbourAuthority
Indicates that one entity holds official authority or administrative control over the operations and management of a harbour associated with another entity.
-
C.
hasHarborOpened
Indicates that a harbor has been officially opened and is available for use or operation.
-
D.
hasHarborFeature
Indicates that something possesses or includes a specific harbor-related characteristic, structure, or facility.
-
E.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dc631c819099027e3a1c755a66 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:04 p.m.