Triple
T6602688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch of Wasdale |
E149037
|
entity |
| Predicate | shoreSettlementType |
P41867
|
FINISHED |
| Object | sparsely populated rural 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: sparsely populated rural area | Statement: [Loch of Wasdale, shoreSettlementType, sparsely populated rural area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoreSettlementType Context triple: [Loch of Wasdale, shoreSettlementType, sparsely populated rural area]
-
A.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
B.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
C.
typicalSettlement
chosen
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
-
D.
typeOfSettlement
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
-
E.
governsSettlementType
Indicates that an authority or administrative body exercises governing control over a particular type or category of settlement.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.