Triple
T31470350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormarn district |
E802841
|
entity |
| Predicate | hasNeighboringCityState |
P198576
|
FINISHED |
| Object | Free and Hanseatic City of Hamburg |
—
|
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: Free and Hanseatic City of Hamburg | Statement: [Stormarn district, hasNeighboringCityState, Free and Hanseatic City of Hamburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringCityState Context triple: [Stormarn district, hasNeighboringCityState, Free and Hanseatic City of Hamburg]
-
A.
isNeighboringCityOf
Indicates that one city is geographically adjacent to or directly borders another city.
-
B.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
C.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
D.
nearByCityState
Indicates that a city is geographically close to or within the same general area as a specified state.
-
E.
hasBorderingStateCapital
Indicates that one state capital city is directly adjacent to or shares a border with another state capital city.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: April 30, 2026, 9:25 p.m.