Triple
T26496683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineering Castle moat section |
E669300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic waterfront segment |
C13058
|
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: historic waterfront segment Context triple: [Engineering Castle moat section, instanceOf, historic waterfront segment]
-
A.
historic wharf
A historic wharf is a preserved waterfront structure once used for docking, loading, and unloading ships, now valued for its cultural, architectural, and maritime heritage significance.
-
B.
historic harbor
chosen
A historic harbor is a waterfront area that has played a significant role in maritime trade, travel, or defense over time and retains physical or cultural features reflecting its past.
-
C.
historic fishing district
A historic fishing district is a coastal or riverside urban area traditionally centered around commercial fishing activities, characterized by preserved maritime infrastructure, cultural heritage, and long-standing fishing-related communities and businesses.
-
D.
historic maritime signal tower
A historic maritime signal tower is a coastal structure once used to communicate navigational information, warnings, and messages to ships at sea through visual signals such as flags, lights, or semaphores.
-
E.
historic shipyard
A historic shipyard is a preserved maritime industrial site where ships were once designed, built, repaired, and launched, often retaining original structures, tools, and waterfront infrastructure that reflect its historical significance.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:09 a.m.