Triple
T23803677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landkreis Nordvorpommern |
E589641
|
entity |
| Predicate | hadHanseaticCity |
P149516
|
FINISHED |
| Object | Stralsund |
—
|
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: Stralsund | Statement: [Landkreis Nordvorpommern, hadHanseaticCity, Stralsund]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHanseaticCity Context triple: [Landkreis Nordvorpommern, hadHanseaticCity, Stralsund]
-
A.
HanseaticCity
chosen
Indicates that a city is or was a member of the Hanseatic League, reflecting its historical participation in that commercial and defensive confederation.
-
B.
firstLargeGermanSettlement
Indicates that the subject is the earliest significant settlement established by Germans in the specified place or context.
-
C.
isHistoricPortOf
Indicates that a location served as a significant port for another place during a past historical period.
-
D.
isBalticPortCity
Indicates that a city functions as a port located on the Baltic Sea.
-
E.
hadCity
Indicates that an entity was formerly associated with or located in a particular city.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c750048c8190899ff611df35b361 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:55 p.m.