Triple
T31535065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisconsin Shipwreck Coast National Marine Sanctuary |
E804582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | underwater cultural heritage site |
C7806
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: underwater cultural heritage site Context triple: [Wisconsin Shipwreck Coast National Marine Sanctuary, instanceOf, underwater cultural heritage site]
-
A.
maritime archaeological site
chosen
A maritime archaeological site is a submerged or coastal location containing physical remains, artifacts, or environmental evidence that reveal past human activities related to seafaring, trade, or coastal life.
-
B.
underwater archaeological trail
An underwater archaeological trail is a designated, interpretive diving route that guides visitors past submerged cultural heritage sites while providing educational information and ensuring their protection.
-
C.
cultural site
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
D.
underwater archaeology unit
An underwater archaeology unit is a specialized team or organizational division dedicated to locating, documenting, and preserving submerged cultural heritage sites using scientific diving, remote sensing, and conservation techniques.
-
E.
scuba diving site
A scuba diving site is a specific underwater location characterized by suitable depth, visibility, marine life, and safety conditions for recreational or professional diving activities.
- F. None of above.
Provenance (1 batch)
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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:03 p.m.