Triple
T10746265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Bremerton |
E253455
|
entity |
| Predicate | subsidiaryFacilityType |
P2836
|
FINISHED |
| Object | marina |
—
|
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: marina | Statement: [Port of Bremerton, subsidiaryFacilityType, marina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsidiaryFacilityType Context triple: [Port of Bremerton, subsidiaryFacilityType, marina]
-
A.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
B.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
subsidiaryOrAsset
Indicates that one entity is owned, controlled, or held as a subsidiary company or asset by another entity.
-
D.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
E.
isNamedFacilityOf
Indicates that a facility bears the official name associated with a particular entity (such as an organization, person, or 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b85d9c8190a66f536e2f22ed04 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.