Triple
T33357465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nysa Łużycka |
E854114
|
entity |
| Predicate | usedAsBorderSince |
P195829
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Nysa Łużycka, usedAsBorderSince, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBorderSince Context triple: [Nysa Łużycka, usedAsBorderSince, 1945]
-
A.
usedAsBorder
Indicates that one entity functions as a boundary or dividing line for another entity.
-
B.
borderUsedFor
Indicates that a border between areas or entities is utilized for a specific purpose, function, or activity.
-
C.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
D.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
-
E.
hasBorderSignificance
Indicates that a border between entities holds particular importance, impact, or relevance in a given context.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 1, 2026, 1:34 a.m.