Triple
T33695848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Muskau |
E863307
|
entity |
| Predicate | hasCrossBorderConnectionWith |
P23990
|
FINISHED |
| Object | Łęknica |
—
|
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: Łęknica | Statement: [Bad Muskau, hasCrossBorderConnectionWith, Łęknica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderConnectionWith Context triple: [Bad Muskau, hasCrossBorderConnectionWith, Łęknica]
-
A.
hasCrossBorderTies
Indicates that there exists a relationship or connection that extends across national or jurisdictional boundaries between the involved entities.
-
B.
hasCrossBorderInteraction
Indicates that there is an interaction, activity, or relationship occurring between entities located in different countries or jurisdictions.
-
C.
hasCrossBorderCenter
Indicates that an entity operates or is associated with a center whose activities, services, or scope extend across national borders.
-
D.
hasBorderConnection
chosen
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
E.
hasCrossBorderArea
Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:43 a.m.