Triple
T11862752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kodori Gorge |
E282197
|
entity |
| Predicate | historicalPeriodOfIntenseConflict |
P32860
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Kodori Gorge, historicalPeriodOfIntenseConflict, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfIntenseConflict Context triple: [Kodori Gorge, historicalPeriodOfIntenseConflict, 1990s]
-
A.
conflictEra
chosen
Indicates that two entities are associated with the same historical period or era of conflict.
-
B.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
C.
startOfMajorConflict
Indicates that one event marks the beginning or initial outbreak of a major conflict between parties.
-
D.
religiousConflictPeriod
Indicates a period of time during which conflicts or hostilities occur that are primarily motivated or structured by religious differences or tensions.
-
E.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.