Triple
T3201443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Beach (Vieques) |
E67060
|
entity |
| Predicate | hasApproximateShoreOrientation |
P45094
|
FINISHED |
| Object | south-facing coast (approximate) |
—
|
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: south-facing coast (approximate) | Statement: [Black Beach (Vieques), hasApproximateShoreOrientation, south-facing coast (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateShoreOrientation Context triple: [Black Beach (Vieques), hasApproximateShoreOrientation, south-facing coast (approximate)]
-
A.
coastOrientation
chosen
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
B.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
C.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or entity.
-
D.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
E.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b046c8819087c0a61c4f9adeb7 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.