Triple
T15360318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ålesunder |
E367271
|
entity |
| Predicate | associatedWithGeography |
P19735
|
FINISHED |
| Object | coastal town |
—
|
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: coastal town | Statement: [ålesunder, associatedWithGeography, coastal town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGeography Context triple: [ålesunder, associatedWithGeography, coastal town]
-
A.
typicalGeographicalAssociation
Indicates a usual or characteristic geographical connection between entities, such as a place commonly associated with a person, group, or phenomenon.
-
B.
associatedWithLocality
chosen
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
-
C.
containsGeographicalArea
Indicates that one geographical area spatially encompasses or includes another geographical area within its boundaries.
-
D.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
E.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4607408190ab281a7f7a8012d3 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.