Triple
T24565485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czeladź |
E607774
|
entity |
| Predicate | borderRiverWith |
P143613
|
FINISHED |
| Object | Upper 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: Upper Silesia | Statement: [Czeladź, borderRiverWith, Upper Silesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRiverWith Context triple: [Czeladź, borderRiverWith, Upper Silesia]
-
A.
borderRiverContext
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
-
B.
bordersAcrossRiver
chosen
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92082a881908896dcdda85559b9 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.