Triple
T18240775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sollerøya |
E436802
|
entity |
| Predicate | locatedInLakeRankContext |
P17985
|
FINISHED |
| Object | one of Norway’s largest inland lakes (Femunden) |
—
|
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: one of Norway’s largest inland lakes (Femunden) | Statement: [Sollerøya, locatedInLakeRankContext, one of Norway’s largest inland lakes (Femunden)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLakeRankContext Context triple: [Sollerøya, locatedInLakeRankContext, one of Norway’s largest inland lakes (Femunden)]
-
A.
isInLake
Indicates that one entity is located within the body of water defined as a lake.
-
B.
isWithinLakeSystem
Indicates that one body of water is contained within, or forms a component of, a larger interconnected lake system.
-
C.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated area.
-
D.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
-
E.
hasNearbyLake
chosen
Indicates that one entity is located close to or in the vicinity of a lake.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e287548190b666a990e5b168b0 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.