Triple
T31470351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormarn district |
E802841
|
entity |
| Predicate | hasNeighboringIndependentCity |
P57276
|
FINISHED |
| Object | Lübeck |
—
|
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: Lübeck | Statement: [Stormarn district, hasNeighboringIndependentCity, Lübeck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringIndependentCity Context triple: [Stormarn district, hasNeighboringIndependentCity, Lübeck]
-
A.
hasNeighboringCityState
Indicates that one city-state is geographically adjacent to or directly borders another city-state.
-
B.
hasIndependentCity
Indicates that a larger administrative region or entity contains a city that is administratively independent from the surrounding local jurisdictions.
-
C.
isNeighboringCityOf
chosen
Indicates that one city is geographically adjacent to or directly borders another city.
-
D.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
E.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 30, 2026, 9:25 p.m.