Triple
T33754501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svelvik |
E864936
|
entity |
| Predicate | locatedAcrossFjordFrom |
P138389
|
FINISHED |
| Object | Hurummarka area |
—
|
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: Hurummarka area | Statement: [Svelvik, locatedAcrossFjordFrom, Hurummarka area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAcrossFjordFrom Context triple: [Svelvik, locatedAcrossFjordFrom, Hurummarka area]
-
A.
locatedInFjordSystem
Indicates that something is situated within or is part of a specific fjord system.
-
B.
hasNearbyFjord
Indicates that one entity is located close to or in the vicinity of a fjord associated with another entity.
-
C.
hasFjord
Indicates that an entity possesses, contains, or is characterized by a fjord as part of its geography or features.
-
D.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
E.
hasNeighborAcrossFjord
chosen
Indicates that one entity is located across a fjord from another entity, such that they are neighbors separated by the fjord.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.