Triple
T35139237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muddusälven |
E1014656
|
entity |
| Predicate | humanSettlementLevelNearby |
P70399
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Muddusälven, humanSettlementLevelNearby, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanSettlementLevelNearby Context triple: [Muddusälven, humanSettlementLevelNearby, low]
-
A.
hasNearbySettlementDensity
Indicates that an entity is associated with a concentration of settlements located within a nearby surrounding area.
-
B.
humanSettlementLevel
chosen
Indicates the degree or intensity of human settlement present in a given area, such as how densely or extensively it is inhabited or developed.
-
C.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
D.
nearbySettlementStatus
Indicates whether a settlement is located close enough to another reference point or area to be considered nearby.
-
E.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ca7c87c81908f1648733f2ea3db |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.