Triple
T34391844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapa Army Base |
E882723
|
entity |
| Predicate | borderDefenseContext |
P58152
|
FINISHED |
| Object | near Russian border |
—
|
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: near Russian border | Statement: [Tapa Army Base, borderDefenseContext, near Russian border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDefenseContext Context triple: [Tapa Army Base, borderDefenseContext, near Russian border]
-
A.
sharesBorderDefenseWith
Indicates that two entities cooperate or coordinate in protecting and defending their shared border.
-
B.
defenceContext
chosen
Indicates the situational, legal, or strategic circumstances under which a defence action or defence-related relationship occurs.
-
C.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
D.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
E.
borderFacilityContext
Indicates a contextual relationship where an entity is associated with, operates within, or is relevant to a border facility or border-control setting.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 1, 2026, 1:59 a.m.