Triple
T33386950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocasset |
E854939
|
entity |
| Predicate | hasCurrentSettlementOnSite |
P171391
|
FINISHED |
| Object | Portsmouth, Rhode Island |
—
|
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: Portsmouth, Rhode Island | Statement: [Pocasset, hasCurrentSettlementOnSite, Portsmouth, Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentSettlementOnSite Context triple: [Pocasset, hasCurrentSettlementOnSite, Portsmouth, Rhode Island]
-
A.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
B.
hasSubsettlement
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
-
C.
currentSettlement
chosen
Indicates that an entity is presently located in or associated with a particular settlement (such as a town, city, or village).
-
D.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
E.
hasPortSettlement
Indicates that a place has a settlement located at or directly associated with a port for maritime or water-based transport.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 1, 2026, 1:35 a.m.