Triple
T2049899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig-Holstein |
E45540
|
entity |
| Predicate | sharesBorderType |
P35564
|
FINISHED |
| Object | land border with Denmark |
—
|
LITERAL FINISHED |
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: land border with Denmark | Statement: [Schleswig-Holstein, sharesBorderType, land border with Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderType Context triple: [Schleswig-Holstein, sharesBorderType, land border with Denmark]
-
A.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
B.
borderText
Indicates that one entity is the textual content displayed along the border of another entity.
-
C.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
languageBorderInvolved
Indicates that a situation, event, or relationship involves or is affected by a boundary between different languages or linguistic communities.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98e10d48190bb96cd1f8ea3c08b |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:39 p.m.