Triple
T36464837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borchali |
E898394
|
entity |
| Predicate | ethnicTensionBetween |
P55763
|
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: [Borchali, ethnicTensionBetween, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicTensionBetween Context triple: [Borchali, ethnicTensionBetween, Georgia]
-
A.
hasEthnicTensionHistory
chosen
Indicates that there has been a history of conflict, strain, or hostility between ethnic groups within the referenced context.
-
B.
interethnicRelations
Indicates the nature and dynamics of interactions, relationships, and attitudes between different ethnic groups.
-
C.
diplomaticTensionBetween
Indicates a strained or conflict-prone diplomatic relationship existing between two entities.
-
D.
ethnoPoliticalConflict
Indicates a relationship in which groups defined by ethnic identity are engaged in political struggle, tension, or violence against one another or against a governing authority.
-
E.
religiousConflictBetween
Indicates a relationship where two entities are in opposition or dispute due to differing religious beliefs, practices, or affiliations.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:10 p.m.