Triple
T24279300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srivijayan ports |
E605495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical maritime ports |
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: historical maritime ports Context triple: [Srivijayan ports, instanceOf, historical maritime ports]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
maritime influence
Maritime influence is the effect that proximity to oceans and seas has on a region’s climate, weather patterns, and human activities, typically moderating temperatures and increasing humidity.
-
E.
former port city
A former port city is an urban settlement that once functioned as a significant maritime trade hub but has since lost its port operations or primary seafaring role due to economic, environmental, or infrastructural changes.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:07 a.m.