Triple
T8807991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockland–North Haven |
E209580
|
entity |
| Predicate | connectsMainlandPort |
P77702
|
FINISHED |
| Object | Rockland, Maine |
—
|
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: Rockland, Maine | Statement: [Rockland–North Haven, connectsMainlandPort, Rockland, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsMainlandPort Context triple: [Rockland–North Haven, connectsMainlandPort, Rockland, Maine]
-
A.
connectedToMainlandBy
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
-
B.
servesAsMainPortOfEntryFor
Indicates that one location functions as the primary gateway or access point through which another entity typically enters a region or system.
-
C.
terminalOnMainland
Indicates that a transportation or service terminal is physically located on the mainland rather than on an island or offshore location.
-
D.
isPortOf
chosen
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
E.
connectsSpecialAdministrativeRegion
Indicates a relationship where one entity is linked or associated specifically with a special administrative region.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd2fadc81908b27e9296885af2b |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.