Triple
T26522615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provisional All-Russian Government |
E669997
|
entity |
| Predicate | sharesBorderConflictWith |
P152442
|
FINISHED |
| Object | Red Army |
—
|
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: Red Army | Statement: [Provisional All-Russian Government, sharesBorderConflictWith, Red Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderConflictWith Context triple: [Provisional All-Russian Government, sharesBorderConflictWith, Red Army]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
hasBorderConflictWith
chosen
Indicates a relationship where two entities share a disputed boundary or are involved in an ongoing or historical conflict over their common border.
-
C.
sharesBorderDefenseWith
Indicates that two entities cooperate or coordinate in protecting and defending their shared border.
-
D.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
-
E.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 27, 2026, 1:29 a.m.