Triple
T35076986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalsfjorden |
E1012332
|
entity |
| Predicate | hasSettlementAlongShore |
P119386
|
FINISHED |
| Object | small villages |
—
|
LITERAL 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: small villages | Statement: [Dalsfjorden, hasSettlementAlongShore, small villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementAlongShore Context triple: [Dalsfjorden, hasSettlementAlongShore, small villages]
-
A.
shorelineSettlement
chosen
Indicates that a settlement is located along or directly adjacent to a shoreline.
-
B.
hasShoreNear
Indicates that one entity is located close enough to another entity’s shore or coastline to be considered nearby.
-
C.
hasLongShoreline
Indicates that an entity possesses an extensive or unusually long shoreline relative to typical cases.
-
D.
hasTransportationCorridorAlongShore
Indicates that there is a transportation corridor (such as a road, railway, or similar route) running along or parallel to a shoreline.
-
E.
hasStructureOnShore
Indicates that a structure is located on or directly adjacent to the shore of a body of water.
- F. None of above.
Provenance (3 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:01 p.m.