Triple
T33021411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Călărași County |
E844921
|
entity |
| Predicate | borderCountryViaRiver |
P143613
|
FINISHED |
| Object | Bulgaria |
—
|
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: Bulgaria | Statement: [Călărași County, borderCountryViaRiver, Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCountryViaRiver Context triple: [Călărași County, borderCountryViaRiver, Bulgaria]
-
A.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
B.
bordersAcrossRiver
chosen
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
C.
transboundaryRiverOf
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
D.
crossBorderRiverSystemOf
Indicates a river system that flows across or forms the boundary between different political or administrative regions associated with the referenced entity.
-
E.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of a river.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:23 a.m.