Triple
T7683714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spring Point Ledge Light |
E174059
|
entity |
| Predicate | connectedToShoreBy |
P51899
|
FINISHED |
| Object | granite breakwater |
—
|
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: granite breakwater | Statement: [Spring Point Ledge Light, connectedToShoreBy, granite breakwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToShoreBy Context triple: [Spring Point Ledge Light, connectedToShoreBy, granite breakwater]
-
A.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
B.
hasStructureOnShore
chosen
Indicates that a structure is located on or directly adjacent to the shore of a body of water.
-
C.
primaryIslandOnShore
Indicates that one island is the main or most significant island located along a particular shore or coastline.
-
D.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
E.
seaConnection
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.