Triple
T34119843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brynica River |
E875090
|
entity |
| Predicate | historicallyMarksBorderBetween |
P47008
|
FINISHED |
| Object | Silesia |
—
|
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: Silesia | Statement: [Brynica River, historicallyMarksBorderBetween, Silesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyMarksBorderBetween Context triple: [Brynica River, historicallyMarksBorderBetween, Silesia]
-
A.
historicallyCircumscribedBy
Indicates that one entity’s historical existence, development, or significance is bounded, defined, or delimited by the historical context or period associated with another entity.
-
B.
historicBoundaryFor
chosen
Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
-
C.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
-
D.
historicalRegionCrossed
Indicates that one entity passes through or traverses the territory of a historically defined region.
-
E.
historicallyDistinctFrom
Indicates that two entities are recognized as separate and not the same in historical context, despite any similarities or connections they may have.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:53 a.m.