Triple
T35630427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirlstane |
E1029568
|
entity |
| Predicate | hasCoastalAccessVia |
P108755
|
FINISHED |
| Object | Port Sorell |
E1033865
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Port Sorell | Statement: [Thirlstane, hasCoastalAccessVia, Port Sorell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalAccessVia Context triple: [Thirlstane, hasCoastalAccessVia, Port Sorell]
-
A.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
B.
connectsToCoastAt
chosen
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
-
C.
hasOnItsCoast
Indicates that a geographic entity (such as a country or region) borders and includes along its shoreline another entity (such as a sea, ocean, or body of water).
-
D.
isCoastalDestinationFor
Indicates that a place serves as a seaside or ocean-adjacent travel destination for a particular person, group, or market.
-
E.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
- F. None of above.
Provenance (4 batches)
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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38914dc2a4819082b8d704c262f72c |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.