Triple
T36461159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balakan |
E898289
|
entity |
| Predicate | borderCrossingRegionWith |
P108638
|
FINISHED |
| Object | Georgia |
—
|
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: Georgia | Statement: [Balakan, borderCrossingRegionWith, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingRegionWith Context triple: [Balakan, borderCrossingRegionWith, Georgia]
-
A.
borderCrossingArea
chosen
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
B.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
C.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
D.
borderCrossingStatus
Indicates the current state or outcome of an entity’s attempt to cross a border (e.g., allowed, denied, pending, or completed).
-
E.
borderCrossingInfluence
Indicates the effect that crossing a border (e.g., political, geographic, or jurisdictional) has on an entity, action, or interaction between 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 3, 2026, 4:10 p.m.