Triple
T11955303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romania and Ukraine |
E284535
|
entity |
| Predicate | borderRegulatedBy |
P3948
|
FINISHED |
| Object | bilateral treaties |
—
|
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: bilateral treaties | Statement: [Romania and Ukraine, borderRegulatedBy, bilateral treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegulatedBy Context triple: [Romania and Ukraine, borderRegulatedBy, bilateral treaties]
-
A.
borderRegime
chosen
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
B.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
C.
borderConfirmedBy
Indicates that the existence or delineation of a border is validated or officially recognized by a specified authority or source.
-
D.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
E.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.