Triple
T37044723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakagígar area |
E916873
|
entity |
| Predicate | closestSettlements |
P138521
|
FINISHED |
| Object | Kirkjubæjarklaustur |
—
|
NE NERFINISHED |
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: Kirkjubæjarklaustur | Statement: [Lakagígar area, closestSettlements, Kirkjubæjarklaustur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestSettlements Context triple: [Lakagígar area, closestSettlements, Kirkjubæjarklaustur]
-
A.
nearbySettlements
chosen
Indicates that one settlement is located close to another settlement in geographic space.
-
B.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
C.
closestSettlementNorth
Indicates that one settlement is the nearest settlement located to the north of another settlement.
-
D.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
E.
closestSettlementSouth
Indicates that one settlement is the nearest settlement located to the south of another 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:14 p.m.