Triple
T29530625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany–Scandinavia |
E749190
|
entity |
| Predicate | hasKeyPortInGermany |
P104217
|
FINISHED |
| Object | Kiel |
—
|
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: Kiel | Statement: [Germany–Scandinavia, hasKeyPortInGermany, Kiel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPortInGermany Context triple: [Germany–Scandinavia, hasKeyPortInGermany, Kiel]
-
A.
locatedInPartOfGermany
Indicates that one entity is geographically situated within a specific region or part of Germany.
-
B.
hasKeyPort
chosen
Indicates that an entity possesses or is associated with a primary or main port used for connection, access, or communication.
-
C.
containsGermanSpeakingArea
Indicates that one entity geographically includes an area where German is predominantly spoken.
-
D.
hasNearbyPortCountry
Indicates that one entity is a country that has a seaport located geographically close to the other entity.
-
E.
isBalticPortRegion
Indicates that a region functions as a port area located on or directly connected to the Baltic Sea.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 4:52 p.m.