Triple
T23924616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krückau |
E602310
|
entity |
| Predicate | hasSettlementAlongCourse |
P143702
|
FINISHED |
| Object | Elmshorn |
—
|
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: Elmshorn | Statement: [Krückau, hasSettlementAlongCourse, Elmshorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementAlongCourse Context triple: [Krückau, hasSettlementAlongCourse, Elmshorn]
-
A.
isSettlementAlong
chosen
Indicates that a settlement is located adjacent to or in close proximity along the course or edge of a specified linear feature, such as a river, road, or coastline.
-
B.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
C.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
D.
hasSubsettlement
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
-
E.
hasSettlementAtFoot
Indicates that a settlement is located at the base or lower slopes of a geographic feature such as a hill or mountain.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1bdf108190b3c04146af8c3b3c |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:42 p.m.