Triple
T33279983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarpaulin Cove Light |
E852015
|
entity |
| Predicate | nauticalAreaServed |
P6297
|
FINISHED |
| Object | approaches to Woods Hole |
—
|
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: approaches to Woods Hole | Statement: [Tarpaulin Cove Light, nauticalAreaServed, approaches to Woods Hole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nauticalAreaServed Context triple: [Tarpaulin Cove Light, nauticalAreaServed, approaches to Woods Hole]
-
A.
nauticalRegion
Indicates that one entity is a maritime or nautical area within which the other entity is located, operates, or is relevant.
-
B.
appliesToSeaArea
chosen
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
C.
maritimePowerServed
Indicates that an entity served in or was part of the naval or maritime forces of a particular maritime power.
-
D.
marineAreaShare
Indicates the proportion of a larger marine area that is occupied, controlled, or otherwise attributed to a specific entity.
-
E.
allowedSeaService
Indicates that an entity is permitted or authorized to perform or accrue service at sea.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.