Triple
T18113985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storholmen |
E433552
|
entity |
| Predicate | lakeRankContext |
P130498
|
FINISHED |
| Object | one of the islands of Norway’s largest inland lakes |
—
|
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 the islands of Norway’s largest inland lakes | Statement: [Storholmen, lakeRankContext, one of the islands of Norway’s largest inland lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lakeRankContext Context triple: [Storholmen, lakeRankContext, one of the islands of Norway’s largest inland lakes]
-
A.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
B.
lakePH
Indicates that a lake has a specified pH value or acidity/alkalinity level.
-
C.
capacityRank
Indicates the relative ordering of entities based on how much capacity (e.g., volume, throughput, or capability) they possess compared to others.
-
D.
mouthLake
Indicates the location where a river or stream flows into and forms part of a lake.
-
E.
lakeOrigin
Indicates that a lake originates from, is formed by, or has its source in a specified geographic or hydrological feature.
- F. None of above. chosen
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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd4c7888190b85c39decdb0333f |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.