Triple
T38471457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Erisort |
E915426
|
entity |
| Predicate | hasNearbySettlementPattern |
P202867
|
FINISHED |
| Object | dispersed rural settlements |
—
|
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: dispersed rural settlements | Statement: [Loch Erisort, hasNearbySettlementPattern, dispersed rural settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySettlementPattern Context triple: [Loch Erisort, hasNearbySettlementPattern, dispersed rural settlements]
-
A.
hasNearbySettlementDensity
Indicates that an entity is associated with a concentration of settlements located within a nearby surrounding area.
-
B.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
C.
hasAdjacentSettlement
Indicates that one settlement is located directly next to or bordering another settlement.
-
D.
nearbySettlementStatus
Indicates whether a settlement is located close enough to another reference point or area to be considered nearby.
-
E.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00c8e617548190bba4cdfbb6f512e0 |
completed | May 10, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_6a00c7e816b88190bd40f5ea2a768c8b |
completed | May 10, 2026, 6:01 p.m. |
| PDg | Predicate description generation | batch_6a00c8e566f4819099fead6ead45af09 |
completed | May 10, 2026, 6:05 p.m. |
Created at: May 3, 2026, 4:31 p.m.