Triple
T30002842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Lübeck (historical region) |
E762216
|
entity |
| Predicate | surroundedTerritory |
P45266
|
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: [district of Lübeck (historical region), surroundedTerritory, Lübeck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surroundedTerritory Context triple: [district of Lübeck (historical region), surroundedTerritory, Lübeck]
-
A.
surroundedCity
Indicates that one city is encircled or completely enclosed by another city or its surrounding territory.
-
B.
coreTerritoryAround
chosen
Indicates that one entity serves as the central or primary territory surrounding or enclosing another entity.
-
C.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
D.
surroundedOnThreeSidesBy
Indicates that one entity is positioned so that three of its sides are directly bordered or enclosed by another entity.
-
E.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794fa4008190bd8861c7934bf8fe |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:42 p.m.