Triple
T26243393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Scammel |
E656374
|
entity |
| Predicate | harborProtected |
P77749
|
FINISHED |
| Object | Portland Harbor |
—
|
NE NERFINISHED |
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: Portland Harbor | Statement: [Fort Scammel, harborProtected, Portland Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harborProtected Context triple: [Fort Scammel, harborProtected, Portland Harbor]
-
A.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
-
B.
hasHarborProtection
chosen
Indicates that an entity provides or is subject to protective measures for a harbor, such as defense, safety, or sheltering functions.
-
C.
harborOwnership
Indicates that one entity possesses legal or recognized ownership rights over a harbor or port facility.
-
D.
harborDescription
Indicates that one entity serves as a harbor or safe anchorage location for another entity, typically providing shelter, docking, or protection.
-
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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d90a5908190a7ccff2bd50ffe73 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:04 p.m.