Triple
T28080493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piłsudski–Petliura Agreement |
E709661
|
entity |
| Predicate | borderDefinedAlong |
P14046
|
FINISHED |
| Object | Zbruch River |
—
|
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: Zbruch River | Statement: [Piłsudski–Petliura Agreement, borderDefinedAlong, Zbruch River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDefinedAlong Context triple: [Piłsudski–Petliura Agreement, borderDefinedAlong, Zbruch River]
-
A.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
B.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
C.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 27, 2026, 8:51 p.m.