Triple
T26129333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overfalls Shoal lightship station |
E659192
|
entity |
| Predicate | trafficServed |
P159977
|
FINISHED |
| Object | commercial shipping |
—
|
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: commercial shipping | Statement: [Overfalls Shoal lightship station, trafficServed, commercial shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficServed Context triple: [Overfalls Shoal lightship station, trafficServed, commercial shipping]
-
A.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
B.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
-
C.
cargoTrafficRank
Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
-
D.
routesTrafficThrough
Indicates that network traffic originating from one entity is directed to pass through another entity as an intermediate path or conduit.
-
E.
servesSeasonalTraffic
Indicates that an entity provides service only during specific seasons or periods of the year, rather than year-round.
- F. None of above. chosen
Provenance (4 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b9202b08190b2dca041b547d64e |
completed | May 2, 2026, 2:34 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:13 p.m.