Triple
T11393793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New London harbor |
E269913
|
entity |
| Predicate | supportsRoute |
P4374
|
FINISHED |
| Object | ferry service to Fishers Island, New York |
—
|
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: ferry service to Fishers Island, New York | Statement: [New London harbor, supportsRoute, ferry service to Fishers Island, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRoute Context triple: [New London harbor, supportsRoute, ferry service to Fishers Island, New York]
-
A.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
B.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
C.
supportsTraffic
Indicates that one entity is capable of handling, carrying, or accommodating the flow or volume of traffic associated with another entity.
-
D.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
E.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80018a58c81908b80dc9abd18d650 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.