Triple
T31396511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Small Boat Register |
E800877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime heritage database |
C12523
|
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: maritime heritage database Context triple: [National Small Boat Register, instanceOf, maritime heritage database]
-
A.
maritime archaeological site
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.
shipwreck museum
A shipwreck museum is a cultural institution that collects, preserves, researches, and exhibits artifacts, stories, and historical contexts related to maritime disasters and sunken vessels.
-
C.
cultural heritage database
chosen
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
D.
historical maritime entity
A historical maritime entity is an organization, vessel, or institution from the past that operated on or was fundamentally connected to the sea, shaping or reflecting the maritime activities, trade, warfare, or exploration of its era.
-
E.
maritime culture
Maritime culture encompasses the traditions, practices, beliefs, and social structures of communities whose lives and identities are closely tied to the sea and seafaring 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.