Triple
T30804418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyck |
E784458
|
entity |
| Predicate | nearHistoricalBorder |
P87896
|
FINISHED |
| Object | border of East Prussia and Congress Poland |
—
|
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: border of East Prussia and Congress Poland | Statement: [Lyck, nearHistoricalBorder, border of East Prussia and Congress Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearHistoricalBorder Context triple: [Lyck, nearHistoricalBorder, border of East Prussia and Congress Poland]
-
A.
nearModernBorderWith
Indicates that one entity is located close to the present-day political or geographic border shared with another entity.
-
B.
nearFormerBorderWith
chosen
Indicates that one entity is located close to where the former border or boundary with another entity used to be.
-
C.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
-
D.
nearBorderBetween
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
E.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6903d362081909535bb042ea5f111 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:42 p.m.