Triple
T31292960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hulk "Concrete Barge" SCOWS (various) |
E797990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime heritage site component |
C16149
|
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 site component Context triple: [Hulk "Concrete Barge" SCOWS (various), instanceOf, maritime heritage site component]
-
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.
maritime structure
chosen
A maritime structure is a man-made construction located in or near bodies of water, designed to support marine activities such as navigation, transportation, resource extraction, or coastal protection.
-
C.
heritage site component
A heritage site component is an individual physical or spatial element within a heritage site that contributes to its overall cultural, historical, or architectural significance.
-
D.
heritage asset
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
E.
component of national historic site
A component of a national historic site is an individual physical or cultural element—such as a building, structure, landscape feature, or artifact—that contributes to the site's overall historical significance and integrity.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:14 p.m.